Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
403 Forbidden using Flask, WSGI and Apache2 Question Question
how do I configure htaccess files in EACH folder I want to protect ? Question Question

Question

Virtual Host websites all show 404 after reboot

Posted March 1, 2017 1.9k views
ApacheDebian

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.

Add a comment
HW102
By:
HW102

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
403 Forbidden using Flask, WSGI and Apache2 Question Question
how do I configure htaccess files in EACH folder I want to protect ? Question Question

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.

×
Submit an Answer
1 answer
jtittle1 March 1, 2017

@HW102

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.

Reply Report

Related

Looking for something else?

Ask a new question Search for more help