A question can only have one accepted answer. Are you sure you want to replace the current answer with this one?
You previously marked this answer as accepted. Are you sure you want to unaccept it?
Write for DigitalOcean
You get paid, we donate to tech non-profits.
Find and meet other developers in your city.
Contribute to Open Source
What can I do to get my website back up after I’m seeing a 504 Gateway Error?
What webserver (apache, nginx) are you running?
Add comments here to get more clarity or context around a question. To answer a question, use the “Answer” field below.
Please follow the steps below -
and updated DNS also but when i ping my domain it still points to the old ipaddress.
I rebooted my droplet, as I've done before, but now I can't connect to it with putty and pinging the IP address from outside results in timeout.
I can use the Console Access feature in Digital Ocean website. Executing e.g. ```ping 18.104.22.168``` results in *destination host unreachable* messages.
Unfortunately I don't have skills to troubleshoot this problem any further. Any suggestions for the next steps?
My hardware is a DO box - 2GB Ram 40GB SSD Disk New York 3 Ubuntu 14.04 x64
I am deploying a web app in MeteorJS and I bump into a console error where it says
WebSocket connection to 'ws://12.123.456.78/sockjs/487/lttjh9gq/websocket' failed: Error during WebSocket handshake: net::ERR_CONNECTION_RESET
My deployment is done using https://github.com/arunoda/meteor-up, standard settings nothing special.
Anyone encountered the same problem and know how to fix this?
I'm running this Rails app on DO (FreeBSD). Lately I've been experiencing extremely slow initial requests after longer periods of inactivity. Subsequent requests are fine.
At first I thought it was my PostgreSQL database or the Rails app itself, but now I doubt that's the case as I just realized SSH connections made simultaneously with those initial requests are equally slow.
Has anybody ever encountered anything similar?