Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

504 Gateway Time-out(Rails one click install)

Posted on February 24, 2017

Hi,

I’ve just installed a Ruby on Rails application by following this tutorial; https://www.digitalocean.com/community/tutorials/how-to-use-the-ruby-on-rails-one-click-application-on-digitalocean . But the app isn’t working, I’m getting a 504 Gateway Time-out. Can anyone point me in the right direction of fixing it?

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Jonathan Tittle

February 24, 2017

@nasdas

Despite the fail_timeout = 0; in the upstream, NGINX relies on proxy_connect_timeout also, which is set to a default of 60s, and according to their documentation, can not generally exceed 75s.

So if proxy_connect_timeout is not set (and it’s not in that guide), it defaults to 60s. If you’re app isn’t responding in that amount of time, you’ll receive a 504 GTO error.

What this means is that when NGINX proxies the request to your app, it’s just not responding quickly enough with a valid response (i.e. 200 or other), so to resolve this, you’d need to take a look at your application and see why it’s not responding.

I’ve tested quit a few of the stock one-click images and they work as intended (the test app works), so I don’t think it’s an issue there, but most likely something within the app you’ve installed and are trying to poxy requests to.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

View all products

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.