Entire Droplet won't load any websites:

Crazy story. I have a few low-traffic websites I have on a droplet. etc

and some development environments on subdomains.

but this morning, I wake up and to my dismay, not a single website is viewable.

DNS settings check out.

I am only at an elementary level with the terminal.

Where do I start to look for answers?

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.

Bobby Iliev
Site Moderator
Site Moderator badge
January 2, 2024

Hi there,

I’ve just visited your sites and I can see that they are returning a 500 error. The 500 error typically indicates a server-side problem, so let’s approach this step by step.

  1. Check Server Logs: The first step is to check your server logs for any specific error messages. Since you’re at an elementary level with the terminal, here’s a simple command to view the last few lines of your web server’s error log. For Apache, use sudo tail -30 /var/log/apache2/error.log, and for Nginx, use sudo tail -30 /var/log/nginx/error.log. This might give you a clue about what’s going wrong.

  2. Server Resources: Sometimes, 500 errors can be due to resource exhaustion. Check if your Droplet is running out of memory or CPU. You can quickly check this with the top command.

  3. File Permissions: Incorrect file permissions can also cause such issues. Ensure that your web files have the correct permissions set. A general rule of thumb is directories should be 755 and files should be 644.

  4. PHP/Database Issues: If your site is PHP-based (like WordPress), check the PHP error logs. You might also want to verify that your database is up and running correctly with systemctl status mysql or systemctl status postgresql, depending on your database system.

  5. Restart Web Server: After checking the above, try restarting your web server. For Apache, use sudo systemctl restart apache2, and for Nginx, use sudo systemctl restart nginx.

Feel free to share the errors from the logs so I could advise you further as well!

Best of luck, and let us know how it goes!


Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Featured on Community

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.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel