Report this

What is the reason for this report?

Can't Determine 504 Bad Gateway Cause

Posted on February 9, 2014

I’m getting a 504 error from Nginx.

When I look in the Nginx error.log.1, I see: “2014/01/21 18:06:02 [error] 698#0: *2 connect() failed (111: Connection refused) while connecting to upstream…”

When I try to look in the Rails production.log, the server returns “Killed”.

When I try to restart Unicorn, I get “master failed to start, check stderr log for details”.

When I run df -h I get: Filesystem Size Used Avail Use% Mounted on /dev/vda 20G 4.1G 15G 22% /

When I run ‘df -i’ I get: Filesystem Inodes IUsed IFree IUse% Mounted on /dev/vda 1310720 144242 1166478 12% /

I tried to find a solution in chat and it was suggested I raise a ticket. Please help. Thanks!



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.

Check unicorn’s error logs, is there anything in there?

Please let me know if you find anything. I have this too. <br> <br>

The developer cloud

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

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.