SSH login error

I have a Windows computer, I made the configuration through Putty creating the key, it was working fine on my machine but inactivity appeared in the Putty, I could not reconnect, “Network Error: Connection time out” appears. I don’t know how to enter through the droplet console. The last thing I did was the apache configuration following the procedure of this link

The machine is turned on and if I enter by IP it still loads the Apache configuration.

Any ideas? How do I access it?

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi @Nataliarojas,

As it has been explained how to connect via the console to your droplet, I’ll recommend you to check a couple of other stuff that might have caused the issues.

Firstly, check if your network is up. You can do that by pinging our Droplet’s IP


Where XXX.XXX.XXX.XXX is you actual IP. If it’s not pinging, then the network is down. You can restart it by going to the console and running

service network restart

Usually, I’ve noticed that when the network has been stopped it’s after a reboot or something similar.If you have done a recent reboot, I’ll recommend checking why the Network didn’t start properly.

Regards, KDSys

Hello, @Nataliarojas

You can follow the link I’m listing bellow in order to access your droplet using the DigitalOcean’s console:

Once you’re logged in you can check if the ssh service is running. You can do that using:

service sshd status

If the service is not active(running) you can restart it:

service sshd restart

and then again check if it’s running. You can also try rebooting the droplet as well, but ideally you would like to see what is causing the issue and not just reboot the server in order to resolve the problem.

Hope this helps!

Let me know how it goes.

Regards, Alex