Droplet stuck: how to determine what happened.

Hi everyone. Today one of my droplets was stuck for some hours. By “stuck” I mean it was up, but all my sites were unreachable, and I couldn’t ssh into the droplet itself. So from DO control panel I just turned it off/on, and all went back to normal. Now, what can I do to check what happened and caused the trouble?

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.

Hello there,

I will recommend checking on what Bobby already mentioned. These are all good starting points to investigate what really happened.

If the issue occurs again you can also try to regain access to your droplet using the DigitalOcean console:

The Droplet Console has a native-like terminal experience, so you can run commands on your Droplet from a familiar command-line interface. It also provides one-click SSH access to your Droplet without the need for a password or manual SSH key configuration.


Hi there,

I could suggest checking your system logs to find some more information on what might have happened.

You could also check the resources utilization graphs in your DigitalOcean control panel. It is possible that the server ran out of RAM for example which caused it to crash.

Additionally, if you are using a service like Nginx, you could also check the Nginx access logs to see if there was some malicious activity:

Let me know how it goes!