Trying to access my website results in an ERR_CONNECTION_TIMED_OUT

Posted January 6, 2020 1.8k views

I took a break over Christmas from developing a webapp and I have came back today to find that I am unable to access my website in my browser, or connect to it by an FTP Client or ping my website’s IP address (Results in Requests Timed Out). My server is hosted on DigitalOcean. Obviously I cannot continue development because I am unable to render my changes or connect in general.

ERRCONNECTIONTIMED_OUT is the chrome error message. Before Christmas everything was working fine, in fact I’m very near completing development.

The issue is the same across browsers, ISPs, mobile networks etc.

DO Rebooted my Droplet
I got this email from DO over Christmas:

“We’ve had to reboot your Droplet as a result of an issue with the physical node that hosts your Droplet. We will continue to investigate the health of this physical node to determine if this was an isolated or systemic issue.

No action is required on your part at this time and we apologize for any troubles this may have caused.”

My website is still down and my tickets have fallen on deaf ears.

What I’ve tried:
Restarting Apache - Apache is running and active
Rebooting my server - Rebooted successfully but no changes
Checked UFW firewall rules - These haven’t changed
Pinging my websites IP - Results in timeouts
Connecting with numerous FTP Clients (Filezilla, WinSCP etc.) - Results in timeouts
It is not a DNS issue - There is no domain name yet, the IP address is being used in this development phase to navigate to the website.
I am unable shh into the droplet.
Are there any other suggestions for actions that I can do to try to remedy this? My Apache is running and I can still view and access my files in MY droplet console.

I can spin up another server if needs be but I really want to figure out what has actually happened so I can learn from it.

Thanks and Happy New Year.

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.

Submit an Answer
1 answer

Hello, @jonathandouglas

If you’re unable to ping the IP address of the droplet and can’t ssh as well, I will recommend you to get back to our support team so they can further investigate and assist you with the issue as the issue with the node might not be sorted yet.

Hope this helps.