Question

Unable to access server after resizing droplet

I just upgraded my droplet to a higher RAM capacity and I used the command “shutdown -h now” to power off. I then resized my droplet and booted it up using the DigitalOcean control panel. Since then, I’m no longer able to SSH into my droplet, as it says “Operation timed out”, and I can’t access my sites as well. The only way is to access through the DigitalOcean Console Access but httpd and sshd seems to be running. I have zPanel installed on my server but the RAM usage seems to be much lower now (100+MB instead of 490MB when everything’s fine). When I try to ping, it doesn’t seem to be able to connect to the internet (unknown host).

Can’t believe that all this happened while I was upgrading my specs. Can anyone help me?

Thanks in advance.

Show comments

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.

why don’t you use puTTy to get in there. <br> <br>you find the instructions here: https://www.digitalocean.com/community/articles/how-to-create-ssh-keys-with-putty-to-connect-to-a-vps <br> <br>if you could get in, then you can run clean to fix the errors. you can also check the log file to see what issues you have.

Hello, please can someone help me too. I am Unable to access server. On the console, It gives me error E486 : Pattern not found: localhost with a RED background colour

I’ve fixed it, checked the log files and apparently it was OpenVPN screwing up. Stopped it and everything’s fine again.