Question

Can't Access Droplet via Putty or Terminal

I am unable to access my digital ocean droplet via putty or terminal. I’m a newbie to all of this. Any help or direction would be appreciated. Thank you!


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.

For any other users having this problem remember to allow access to port 22 for ssh in your firewall settings.

ufw users $ sudo ufw allow 22

Hi there,

Are you getting ping to the droplet? Have you made any recent changes to the droplet configuration (like changing firewall rules)?

You can use the DigitalOcean console to regain access to your droplet.

The Recovery Console provides out-of-band access and is available regardless of your network settings. It emulates the access you would have if you were sitting down with a keyboard and monitor attached to the actual server. You can use this feature to log in and revert bad settings to regain normal access.

https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-console/

Regards

Hi @xMudrii @ryanpq,

I blurred it out because I didn’t know what was important or should be kept secret. I had my developer look and he’s having issues to. I logged a ticket.

But this is what we found so far:

Can’t login at all. Even at the console access from UI, it won’t budge. I created a live snapshot of the droplet, created a new droplet from that, same issue. I power cycled the original droplet, still can’t login through either ssh or the console access.

Couple of errors jumping out from the console access:

init: startpar-bridge (mountall–stopped) main process (161) terminataed with status 255

every time, the last message I can get from console access is:

random: nonblocking pool is initialized.

I can’t access it at all.

Another error in the console access (I can’t type anything, just gives me a few lines on display)

init: error while reading from descriptor: Bad file descriptor