Getting Time-out error when trying to deploy Rails 4 app on Nginx

Hey Timo, <br> <br>Is this still the same issue as in: <br> <br>https://www.digitalocean.com/community/questions/504-gateway-time-out-nginx <br> <br>Let’s try and gather some more information to help debug this. How are you running your app? Could you post your Nginx configuration? Any application specific configurations?

Hey Andrew, <br> <br>Yes, indeed, it’s still the same issue. <br> <br>I basically followed this tutorial and didn’t do any changes to the configuration files generated by the 1-click-installation: <br> <br>This would be my /home/unicorn/unicorn.conf: <br> <br>listen “127.0.0.1:8080” <br>worker_processes 2 <br>user “rails” <br>working_directory “/home/rails” <br>pid “/home/unicorn/pids/unicorn.pid” <br>stderr_path “/home/unicorn/log/unicorn.log” <br>stdout_path “/home/unicorn/log/unicorn.log”

I came across a very similar issue, and here’s what worked for me:

When I used the one-click Rails creation, it defaulted to Ruby 2.0.0. I used RVM commands to change this to 1.9.3. Changing it back to 2.0.0 as the default, re-running bundle install (and the whole kit and kabootle of “bundle exec rake db:migrate”, “bundle exec rake assets:precompile”), and restarting the Unicorn service (“service unicorn restart”), the 504 error was gone!

I don’t have anything really holding me back to 1.9.3, so for me, I can just update my development environment to match. I’m not sure what the solution would be otherwise… perhaps building the RoR environment from scratch on a fresh Ubuntu droplet, vs using the one-click option?