I can not access my DigitalOcean droplet with ssh or the DO console
Can not ping the server
Access has work fine for 3yrs, the dev logins almost daily.
No one has made any changes to the configuration files or firewall or iptables
Kernal was updated about 5 months ago without a problem
I tried accessing the iptables but get the message that the file does not exist.
I tried re-installing with
sudo apt-get update && sudo apt-get install linux-image-uname -r && sudo apt-get install linux-headers-uname -r
But I get this https://www.screencast.com/t/QKNPAJOIc
I have NOT power-cycled the droplet, I am afraid if I do that it will not power back up
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!
Hello, @timothylhanson
If you’re unable to access the droplet via ssh and from the console in the control panel as well, I will recommend you to get in touch with our amazing support team and they will check this for you.
Also once you have contacted our team, please provide me with the support ticket number so I can follow up this for you.
Regards, Alex
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.