similar to: 400 bad request

Hey, Just wondering if anyone else has noticed this. I''m using thin+puppetmasterd+nginx. If i add a host, sign it''s key, run puppetd successfully on it all is good, as expected. If i then revoke/clean the key on the master server, leave the box running, startup another host set the hostname to be the same as the old, generate new keys/have them signed. The original box is still

Hi, I''ve created two Nginx patches (see at the end of this message) to allow a simpler Nginx configuration for your Mongrel puppetmasters. The two main issues with Nginx in front of puppet were: * no CRL support * no optional certificate verification (and thus we''re forced to have two separate configs on two different ports, and to use --ca_port). Now, it is as simple as

Thank you all. Except from the buffering it was the fact that I used "localhost" instead of 127.0.0.1 in the proxy_pass. Now my configuration is: location /stream1/ { proxy_buffering off; proxy_ignore_client_abort off; proxy_intercept_errors on; proxy_next_upstream error timeout invalid_header;

I am using mongrel_cluster with mod_proxy_balancer and would like to enable compression (assuming it improves throughtput) and limit file size upload. I configured mod_deflate and LimitRequestSize in Apache, but in my trials looks like the proxied calls bypass those directives (the conf goes below). Is there a way to get this? -- fxn # Adapt this .example locally, as usual. # # To be

Hi All, I am setting up puppetmaster with nginx and passenger and separating the Puppetmaster primary CA server. I have 3 host loadbalancer01 - Nginx doing LB on IP address and also running puppetmaster with passenger under 127.0.0.1 (port 8140). primaryca - Puppetmaster Primary CA pclient - Puppet Client The did the following steps: On Primary CA server: ---------------------------- cd

I''m using a cluster of mongrels behind an apache 1.3 proxy pass. I''ve been passing the request to pen, which in turn balances the cluster of mongrels. Now, I''d like to be able to use a different server to send the static files created by the rails application, so I tried to replace pen with nginx. Everything seems to work fine except the environment variable REMOTE_ADDR.

We've tested this as working relatively well, disable buffering is the major key if I recall. Otherwise the NGINX server loads up data before handing off to the client. server { listen 80; server_name my_dns_name.tldn; location / { proxy_buffering off; proxy_ignore_client_abort off; proxy_intercept_errors on;

Hi, I have an Nginx http proxy server with SSL. What I want to do is: If a client that has a certificate is trying to access the server's address, he is to be redirected to our production server, to certain URL. If a client doesn't have a certificate, he is to be redirected to the same production server, but a different URL. The problem is that if the client doesn't have a

Hi guys, I''m trying to do the following in my template: location <%= location %> { proxy_pass <%= proxy %>; <% if scope.lookupvar(''nginx::resource::location::proxy_header'') then scope.lookupvar(''nginx::resource::location::proxy_header'').each do |header| %> proxy_set_header <%= header %> <% end

In Rails 2.3.x, you can override render_optional_error_file like so: # ApplicationController.rb protected def render_optional_error_file(status_code) render :template => "errors/500", :status => 500, :layout => ''application'' end However, Rails 3 no longer has render_optional_error_file. Instead, you need to overriderescue_action_in_public, which I do:

Dear friends, I followed the guide on http://techoctave.com/c7/posts/16-how-to-host-a-rails-app-with-phusion-passenger-for-nginx and successfully deployed two apps on the same web server, some months ago. Then when I upgraded to Rails 2.3.13.rc1 everything seems to be OK, but when I visit my app with the browser all that I get is the Welcome page from Nginx. Here is my nginx.conf:

Looking over the ServerError code there is no built in way to tell camping to log its errors is there? I suppose the answer it to instantiate a logger, inherit ServerError, call super and pass the return into the logger? If we using fcgi on production, does the ServerError get called, or only the server_error in fcgi.rb? Mainly I''m wondering if there is just one place I can handle

I was getting some "application failed to start properly" pages, but production.log was not showing anything. Looking closer I''ve noticed that server_error.log (the apache log) was giving lines like: "malformed header from script. Bad header=<html>: dispatch.fcgi, referer:" I was able to determine the cause, and that was that some pages were starting with a space

IPv4 addresses started looking very ugly the first time I got IPv6 working on bogomips.org. In case somebody else can''t stand how IPv4-mapped-IPv6 addresses look, the workaround is to use two listeners and ensure the IPv6 one is ipv6only. Unicorn itself supports IPv6, too, but nobody uses/needs it. I''ll add :ipv6only support shortly (probably tomorrow). >From

On the server [root@bangvmpllDA02 logs]# ruby -v ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] [root@bangvmpllDA02 logs]# puppet --version 3.0.1 and [root@bangvmpllDA02 logs]# service nginx configtest nginx: the configuration file /apps/nginx/nginx.conf syntax is ok nginx: configuration file /apps/nginx/nginx.conf test is successful [root@bangvmpllDA02 logs]# service nginx status

Package: xcp-squeezed Version: 1.3.2-9 Severity: important When trying to start a guest I get: # xe vm-start name-label=squeeze-2 The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem. message: Failure("The ballooning daemon is not running") If I then manually run "/etc/init.d/xcp-squeezed

éÚÍÅÎÅÎÉÑ × nginx 0.8.47 28.07.2010 *) éÓÐÒÁ×ÌÅÎÉÅ: ÐÅÒÅÍÅÎÎÁÑ $request_time ÉÍÅÌÁ ÎÅ×ÅÒÎÙÅ ÚÎÁÞÅÎÉÑ ÄÌÑ ÐÏÄÚÁÐÒÏÓÏ×. *) éÓÐÒÁ×ÌÅÎÉÅ: ÏÛÉÂËÉ, ÐÅÒÅÈ×ÁÞÅÎÎÙÅ error_page, ÎÅ ËÜÛÉÒÏ×ÁÌÉÓØ. *) éÓÐÒÁ×ÌÅÎÉÅ: ÅÓÌÉ ÉÓÐÏÌØÚÏ×ÁÌÓÑ ÐÁÒÁÍÅÔÒ max_size, ÔÏ cache manager ÍÏÇ ÚÁÃÉËÌÉÔØÓÑ. ÏÛÉÂËÁ ÐÏÑ×ÉÌÁÓØ × 0.8.46. -- éÇÏÒØ óÙÓÏÅ×

Hello all, I''d like to have nginx+passenger show the custom (Default) error pages when a HTTP 500 error occurs in my app. I am running a rails 2.3 app on nginx 1.2 with passenger 3.0.7 Here is my nginx config file: #user nobody; worker_processes 16; error_log /opt/nginx/logs/error.log info; pid /opt/nginx/logs/nginx.pid; worker_rlimit_nofile 32768; events {

Изменения в nginx 1.23.4 28.03.2023 *) Изменение: теперь протокол TLSv1.3 разрешён по умолчанию. *) Изменение: теперь nginx выдаёт предупреждение при переопределении параметров listen-сокета, задающих используемые протоколы. *) Изменение: теперь, если клиент использует pipelining, nginx закрывает соединения с ожиданием

Hi there. I needed to recompile xapi to fix a bug that was resolved regarding vdi-create not setting the sharable flag. I used the sources provided in the source-1.iso from xen.org. Everything is good in this regard, and creating a vdi that has "sharable=true" is possible, but I had a problem that forced me to revert to the older copy of the xapi binary because my XCP box was now being