I have a droplet running Ubuntu 22.04 (region SFO3). It runs a webserver and I access via ssh or the DigitalOcean console.
I just updated the software using apt update and apt upgrade. Then, because there was a kernel update, I rebooted the droplet using shutdown -r +1 and exited my ssh connection.
After it rebooted, I could no longer ssh into the droplet returning error ssh: connect to host webdrop2 port 22: Connection refused
I cannot get into it from the DigitalOcean console either. The console attempts, fails, and says SSH Connection Lost with a button to read Console Docs and another to Close the window.
I can verify that the droplet is running. I can ping it from my private VPN (running on 10.1.1.x) and the server is serving up web-pages properly.
I don’t have a Plan B for getting console access to the droplet since I always expected the DigitalOcean console to work in a pinch. How can I get console access?
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.
When I wrote the question, I had already powered down and up the droplet without resolving the issue.
After writing the question, it just spontaneously recovered ssh connectivity. Still, the console does not work, but I’ll go poke around and try to figure out what happened. I speculate that perhaps it was just some service taking a long time to initialize and perhaps the sshd was waiting for it.
The problem seems to have been spurious and has gone away.