How To Solve Error: Connection timed out

Hello friends , My website has suddenly stopped, and it is no longer working at all. I have shut down and restarted Droplet several times, but to no avail, and I don’t know why. Even I couldn’t access my server at all either. **

through my console gives me this error:

  • failed to start console session please close this window and try again or
  • error:failed to get droplet info

or via ssh:

- ssh: connect to host x.x.x.x port 22: Connection timed out
## or via Ftp:
- Network error: Connection to "x.x.x.x" timed out.
So I think the problem is in the server. what should I do and I can't completely access my files. Can anyone help me please as soon as possible.

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Purnima Kumari
DigitalOcean Employee
DigitalOcean Employee badge
March 15, 2023

Hello @tarekhussien53

It looks like your IP address is not reaching to reach port 22 or the root login method is not on in your droplet. The issue seems to be with port 22 or firewall. If you are using the cloud firewall, disable the same for time being and regain access to the Droplet.

Otherwise try to get access via the DigitalOcean console in order to restore the access to your droplet.

If not please refer the document here

Site Moderator
Site Moderator badge
August 23, 2023

If you can’t access your droplet via SSH, console, or FTP, it’s indeed a severe issue. Let’s walk through a step-by-step approach to potentially resolve this:

  1. Console Access via DigitalOcean Dashboard:

    • Log in to your DigitalOcean Dashboard.
    • Select your droplet and try accessing it via the ‘Access’ tab by clicking on ‘Launch Console’.
    • If this fails as well, then the droplet might be in a non-recoverable state from your end.
  2. Network Settings:

    • Check if the droplet’s firewall settings in DigitalOcean haven’t been altered to block all incoming traffic, especially to port 22 (SSH).
    • Also, ensure that your IP address hasn’t been accidentally blocked by any security tools or firewall rules you’ve set up.
Site Moderator
Site Moderator badge
March 15, 2023

Hello @tarekhussien53

If you filter any traffic to your droplet via a Cloud Firewall you can temporary disable all rules in order to regain access to your server.

On the other hand if you filter traffic on port 22 via UFW you can then use the DigitalOcean console in order to restore the normal access to your droplet.

Hope that this helps!

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel