Show all posts by user
A portal to and from the mailing list.
upstream timed out - 11 years ago
I am a newbie. I'm running Ubuntu, Nginx and 5 Thin servers - that serve up a Ruby on Rails app. The system hangs about once a day. The Nginx log has this error: 2013/07/11 10:06:46 21344#0: *201 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.10.11, server: , and 2013/07/11 10:05:11 21345#0: *225 an upstream response iby Reddirt - Nginx Mailing List - English
Re: The service is not available. Please try again later. - 11 years ago
OK - I now have Nginx running the 5 Thin app servers! Thanks for the help!by Reddirt - Nginx Mailing List - English
Re: The service is not available. Please try again later. - 11 years ago
I got past that error and now the nginx error log has this: 2013/03/14 14:22:10 1537#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.20.3, server: , request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "ndeavor.ameipro.com" 2013/03/14 14:22:10 1537#0: *1 connect() failed (111: Connection refused) wby Reddirt - Nginx Mailing List - English
Re: The service is not available. Please try again later. - 11 years ago
This is my nginx.conf file. Does it look OK? https://dl.dropbox.com/u/35302780/nginx.confby Reddirt - Nginx Mailing List - English
The service is not available. Please try again later. - 11 years ago
I'm trying to get a Bitnami Rails running with Nginx and Thin. I've got Thin servers running on: bitnami@linux:/opt/bitnami$ thin -C projects/ndeavor/current/config/thin.yml start Starting server on 127.0.0.1:3000 ... Starting server on 127.0.0.1:3001 ... Starting server on 127.0.0.1:3002 ... Starting server on 127.0.0.1:3003 ... Starting server on 127.0.0.1:3004 ... I'veby Reddirt - Nginx Mailing List - English
Re: nginx: [emerg] invalid host in upstream - 11 years ago
OK - we can close this thread. But, I'm going to start a new one because I still can't get to my Rails app.by Reddirt - Nginx Mailing List - English
Re: nginx: [emerg] invalid host in upstream - 11 years ago
My Rails app has this in production.rb: config.serve_static_assets = false When I run Thin by itself, I have to make that true. I thought with Nginx it would stay false.by Reddirt - Nginx Mailing List - English
Re: nginx: [emerg] invalid host in upstream - 11 years ago
I restarted. Now I'm getting the website without the CSS. I thought Nginx would provide the static webpages including CSS. How can I tell if Nginx is running properly? Sorry - This is my first time trying this.by Reddirt - Nginx Mailing List - English
Re: nginx: [emerg] invalid host in upstream - 11 years ago
It looks like Bitnami expects the Rails app to be in url/appname. So, I just removed the /ndeavor from the thin.yml and from nginx.conf. This is what my thin.yml looks like now: https://dl.dropbox.com/u/35302780/thin.yml And this is my nginx.conf: https://dl.dropbox.com/u/35302780/nginx.conf I'm using Bitnami Rails stack that runs Ubuntu. I now start the Thin with this: thin -C thinby Reddirt - Nginx Mailing List - English
nginx: [emerg] invalid host in upstream - 11 years ago
I'm trying to run a Rails app using Nginx with 5 Thin servers. I created the thin.yml file and when I run the start command, I get: bitnami@linux:/opt/bitnami/projects/ndeavor/current/config$ thin -C thin.yml start Starting server on 127.0.0.1:3000 ... Starting server on 127.0.0.1:3001 ... Starting server on 127.0.0.1:3002 ... Starting server on 127.0.0.1:3003 ... Starting serby Reddirt - Nginx Mailing List - English
 |
 |
 |
 |
|