Hi – need advice on how to deal with a DO droplet problem. We cannot ping the ip address of the droplet. A few days ago it was accessible – now it’s not. There was no changes to the server from my side. DO tech support says everything is fine and we need to migrate to a newer version of Ubuntu – how would one do that if we can’t access it? We already launched the recovery console – the situation is the same – still can’t access the droplet.
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.
Heya,
As mentioned if you’re still experiencing the issue and you’ve already contacted our support team, you can provide me with the ticket reference number and I should be able to get this checked for you.
Regards
Heya @brobert,
What do you see in the Recovery Console or can you access the Droplet from it at all?
https://docs.digitalocean.com/products/droplets/how-to/recovery/recovery-console/
If you can’t, try to reboot your Droplet and see if that helps.
If it doesn’t and you still can’t access your Droplet, please provide as much detail as possible to your existing DigitalOcean support ticket. The support should be able to help you in the situation.
Hi there,
If you’ve already tried the recovery console without success, and assuming the Droplet is running but inaccessible, here are a few potential solutions you might consider:
If you haven’t already, perform a power cycle through the DigitalOcean control panel. This can sometimes resolve issues if the Droplet has become unresponsive.
You could try creating a snapshot of your Droplet and then migrating it to a new Droplet with a newer version of Ubuntu.
If you’re in the recovery environment, it’s possible to check the system logs and see if there are any evident issues like file system corruption, kernel panics, or other system errors:
If none of these steps work, or if you’re unsure how to proceed with them, please provide as much detail as possible to your existing DigitalOcean support ticket. The support should guide you through the process, especially if you’re unable to access the Droplet through standard means.
Hope you regain access soon.
Best,
Bobby