Question
How To Solve Error: Connection timed out
- Posted on March 14, 2023• Last validated on November 24, 2023
- FirewallNetworkingSecurity
Asked by tarekhussien53
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.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.
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.
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
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:
Console Access via DigitalOcean Dashboard:
Network Settings:
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.
https://docs.digitalocean.com/products/networking/firewalls/
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.
https://docs.digitalocean.com/products/droplets/resources/recovery-console/
https://www.digitalocean.com/community/tutorials/how-to-set-up-a-firewall-with-ufw-on-ubuntu-20-04
Hope that this helps!