ssh root@2**.1**.1**.1** ssh: connect to host 2**.1**.1**.1** port 22: Connection timed out
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.
Sign up for Infrastructure as a Newsletter.
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Heya,
A timeout can occur and does not mean that an issue has ocurred. Sometimes ssh-clients have session timeouts that can happen if inactivity occurs for some time.
You can ensure that the droplet is online and determine if the issue is within the ssh-client or with the droplet itself.
You can always use the recovery console if normal ssh access is unavailable. The console can be used in emergency cases to regain access to your droplet.
https://docs.digitalocean.com/products/droplets/how-to/connect-with-console/
Hope that this helps!
Hello, @biprajitkarmakar
Experiencing a “Connection timed out” error when trying to SSH into your server can be due to various reasons, such as network issues, incorrect SSH command syntax, server configuration, or firewall settings. Here are some steps you can take to troubleshoot and resolve the issue:
Here’s an example of using the verbose mode to get more information:
ssh -vvv root@2**.1**.1**.1**
I hope my suggestion is helpful for you.
Heya @biprajitkarmakar,
Make sure your Droplet is running, try to ping your Droplet’s IP address. If it doesn’t time out then you can use the DigitalOcean Recovery or Web Console to enter:
Web Console: https://docs.digitalocean.com/products/droplets/how-to/connect-with-console/
Recovery Console: https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-console/
Once inside you should be able to troubleshoot further. One reasone could be that you don’t have enough space on your Droplet or your firewall is blocking port 22.
IF your droplet doesn’t ping, try to reboot it and see if that helps. If it doesn’t it’s best to contact DigitalOcean’s support
Hope that helps! - KFSys.