I have a Rails app running with Thin, and I want Nginx to act as a reverse proxy to pass all the requests under a given location to the Thin server.
From all that I’ve read (and it’s been quite a lot) it seems that the most popular solution is to have the following site configuration file:
upstream thin {
server 127.0.0.1:3000;
}
server {
...
location /thin {
proxy_pass http
I don't know how troubleshoot this. I get "503 Service Unavailable" http error for all "nginx upstreams" proxy passing calls to haproxy fast_thin and slow_thin ( server 127.0.0.1:3100 and server 127.0.0.1:3200 ), which loadbalance on 6 Thin servers ( 127.0.0.1:3000 .. 3005 ). Static files like /blog are currently fine. The falldown is: nginx on port 80 - haproxy on 3100 and 3200 - thin on 3000 ..
I have an environment that uses thin client technology. Many thin clients connect to a central server, log in, and get an X session under their username. All requests to the internet come from the master server's IP.
I would like to set up a proxy to log traffic for diagnostic purposes, as users visiting cretin websites have been known to drive up the load on the server.
I've been using Monit to monitor my Thin server and everything was working until I upgraded my Rails version from 2.3.4 to 2.3.14. Now when I try and start Thin using monit it gives me an unfound gem error:
Missing the Rails 2.3.14 gem.
I am working on a rails app which runs on localhost:3000. I want example.com to point to localhost:3000. I edited the /etc/hosts file but it doesn't take port number so the request goes to apache. I want apache sites to work as they are but redirect example.com to rails server.
Please suggest the best way to achieve this.
I previously ran an two Ruby and Rails applications, one of them by using rails console command, the another one using Apache trough Phusion Passenger. Both applications ran in same IP, the only difference was the application running wih rails console was accesible from port 3000.
Now, I would like to run both apps with Apache, but I know what exactly configure to do that.
Testing a socket.io application in the PROD environment for the first time, we found that while the xhr-polling transport (Ajax long polling) works, the websocket transport does not.
Looking at the data transmitted using Fiddler, I can see that the
UPGRADE happens and
the first message from the server (5 bytes gross) arrive at the client.
The client then sends a couple of messages to the server
I'm using Apache to serve static content, and then reverse proxy-ing to a Rails server to process dynamic content, some of which can take a long time to generate.
I have some thin config files (generated with sudo thin install) which are slightly modified (only paths where they're located).
I can start them just fine with /etc/init.d/thin start, but if the server is restarted, they're not auto started.
Email this page
