Question

Why is the API down even after trying sudo reboot?

So somebody used one of the API endpoints incorrectly, causing the entire application to crash and I tried to reboot the droplet with the command sudo reboot but the API is still down. Is there any way to restart the server and resolve this issue?

This is the banner: SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.6


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.

Hi there,

It would really depend on how you’ve built your API (eg. if you’ve used Node.js, PHP, Django or etc.) and also how you’ve deployed it.

Usually, in such cases, you could quickly check the commands that were previously executed on your server using the history command, which should help you identify what commands the last person who set that all up for you used.

In some cases, if the app was deployed without enabling auto-restart after a reboot, this would explain why your app is not starting.

What you should also check is your API logs to see what errors might be occurring and preventing your app from starting.

Feel free to share more details about your setup so I could try to advise you further.

Best,

Bobby