Virtual Host websites all show 404 after reboot

Hi, I use virtual hosts to host multiple wordpress sites and after I used the command ‘sudo reboot’, all of the sites which were fully working before now return 404 not found pages.

I’ve checked the virtual host files and the DocumentRoot is pointing to the correct directories, I’ve looked at the logs and they seem normal (posted below), I checked the permissions and searched Google for an answer but I’m yet to find one.

Any help or guidance would be greatly appreciated.

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.


It doesn’t appear that the logs posted, so if you could, please try posting them again :-). Beyond the logs, please also post your VirtualHost configuration(s).

A simple reboot of the Droplet shouldn’t turn working websites in to something that no longer works, so there has to be something else at play – at least that would be my initial thought as rebooting shouldn’t change anything.

A reboot may fail to start a service if you don’t have proper init.d or systemd scripts for the service in question, but it shouldn’t alter something that doesn’t normally change unless modified by hand or through a script.