Hey everyone,
I rebooted my Ubuntu 22.04 Droplet earlier today from the DigitalOcean dashboard, and now I can’t connect via SSH. It just times out every time. The droplet shows as “running” in the control panel, but I can’t ping it or access it in any way.
I didn’t make any firewall changes recently, and I’m using the same SSH key that worked before. I’m worried something got stuck during the reboot.
Is there any way to access the console or fix it without destroying the Droplet?
Thanks in advance!
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!
Accepted Answer
Hi,
You can try using the Recovery Console from the DigitalOcean dashboard. It usually works even if SSH isn’t responding.
https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-console/
Once you’re in, check if the SSH service is active with sudo systemctl status ssh. You can also inspect the logs under /var/log/syslog or /var/log/cloud-init.log to see if anything went wrong during reboot.
If the Droplet seems completely stuck, you can boot into Recovery Mode and manually fix or inspect config files from there.
And if you’re still stuck, reach out to support at: https://do.co/support
They might be able to help without needing to destroy the Droplet.
- Bobby
The recovery console is intended for cases like this when the ssh service is not responding.
https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-console/
Once you’re in, check:
sudo systemctl status ssh
and look at logs in /var/log/syslog or journalctl -xe for clues.
If needed, you can also use Recovery Mode, mount your disk, and fix config files manually.
And if it’s still stuck after that, open a support ticket at do.co/support — they can help get you back up without destroying the Droplet.
Hi,
You can try using the Recovery Console from the DigitalOcean dashboard. It usually works even if SSH isn’t responding.
https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-console/
Once you’re in, check if the SSH service is active with
sudo systemctl status ssh. You can also inspect the logs under/var/log/syslogor/var/log/cloud-init.logto see if anything went wrong during reboot.If the Droplet seems completely stuck, you can boot into Recovery Mode and manually fix or inspect config files from there.
And if you’re still stuck, reach out to support at: https://do.co/support
They might be able to help without needing to destroy the Droplet.
- Bobby
Thank u…
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.