similar to: Nginx, Mongrel, Proxy and REMOTE_ADDR

Hi There, Im running an amazon instance with nginx proxying to a unicorn sock. For some reason, even though i specify the production environment, when being visited by nginx, the site shows errors in development form. Interestingly, when running on a port rather than a sock, if i visit that port, the errors are rendered as normal with a 500 page, the same port, throught nginx, shows errors

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

Hi all, I want to do a proxy to icecast (:8000) with nginx (:80). Its working for me, stream is running on port 80, but on the first loading is "pending" For a long time before its starts play. Who using the "proxy_pass" on nginx and can help? Thnx. -------------- next part -------------- An HTML attachment was scrubbed... URL:

It works well when I use webrick. The config of nginx is from puppet wiki, some logs is below, what''s wrong? puppet version:0.25.4 client: ... ... debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/state/state.yaml]: Changing mode debug: /File[/var/lib/puppet/state/state.yaml]: 1 change(s) debug:

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

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

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;

Hi everybody, I just suscribe to the list because I have a problem using mongrel and mongrel_cluster... I setup a server (debian unstable wich provide apache 2.2.3 as a pakage) but I have an error when I try to access my application : ERROR 403 : Forbidden, You don''t have permission to access / on this server. When I check apache''s logs I found that : [warn] proxy: No

Hi, Im using nginx and rails for my site which contains url with georgian letters ie განცხადებები so something like http://gancxadebebi.ge/ka/%E1%83%92%E1%83%90%E1%83%9C%E1%83%AA%E1%83%AE%E1%83%90%E1%83%93%E1%83%94%E1%83%91%E1%83%94%E1%83%91%E1%83%98 It is mainly working perfectly but sometimes I receive request with truncated url ie 1 -

Hello! Today I''m announcing a "soft but official" release of Mongrel 0.3.13.4 for the Unix fans in the crowd. It''s been running stable for quite some time now for many people, and should be great for nearly everyone. You can read the announce at: http://mongrel.rubyforge.org/ This release includes new versions of mongrel_upload_progress and mongrel_cluster.

Eric, think I came across an issue with the parser in unicorn, with a request (due to 2 layers of nginx proxying) coming across with both a X_FORWARDED_PROTO and a X-Forwarded-Proto header. From the socket (in HttpRequest) - we get: X_FORWARDED_PROTO: http X-Forwarded-Proto: https which is parsed to HTTP_X_FORWARDED_PROTO"=>"http,https There was a passenger ticket that

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

I''ve run into an issue with my rails application being unable to properly set cookies on Mongrel 0.3.18. If I run the simplified code below in Mongrel 3.14.4, both cookies are properly sent to and saved by the browser. With the same code in 0.3.18, only the auth_token cookie is created (if I switch them, only the userid as it will only properly create the first cookie in the list.)

I am considering upgrading to either Mongrel 1.1.1 or 1.0.4, and Mongrel-cluster to 1.0.5. Are there any gotchas or issues I need to be aware of? Also where can I find the release notes for the various releases? (The ones I found seem very sparse). Thanks, Brian -------------- next part -------------- An HTML attachment was scrubbed... URL:

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;

I just ran into an issue with a new mongrel install on Win32. When trying to run mongrel from RadRails 0.7.2 on win32, I got an error while loading that it couldn''t locate mongrel_service. C:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_require'': no such file to load -- C:/ruby/lib/ruby/gems/1.8/gems/mongrel_service-0.3.1/lib/mongrel_service/init.rb

While I could figure this out, I''m asking here first to see if anyone has already dealt with/created this. I''m running a mongrel cluster, running 4 mongrels on ports 8001-4. I''m using capistrano to deploy. And I''d like to use monit to check to make sure everything is running nice. I''d like to have monit restart only single mongrels if they fail, and

hey all, I have an app working great with apache2 and mongrel_cluster. However, I''m trying to run another application and now when I go to app1.comit falls to app2.com and the opposite. That''s probably because I messed up somewhere with the cluster. this is the content of my conf.d/app1.proxy_cluster.conf: <Proxy balancer://mongrel_cluster> BalancerMember

I''m setting up a new server in anticipation of switching from lighttpd+fcgi. My application isn''t completely imported yet, so I don''t expect it to work. For instance right now when pulling up my app from localhost I get my Ruby/Rails MySQL error message. But when I pull it up from a remote computer I get a proxy error from Apache: ====================== Proxy Error