Attention: while using HTTPS. configuring a VirtualHost for port 443. I had to replicate the same configs Location media Require all granted Location on default-ssl.conf for my CSS to be loaded. (My problem was that the login page was accessible, but no CSS nor other media files were loaded. ) YuriC Jun 15 ’15 at 21:00
This drove me absolutely nuts for a day an a half but I found a solution if all other solutions have been tried unsuccessfully.
- Go to activity Monitor (spotlight search for: activity)
- In activity monitor search for httpd which is the Apache service
- Select the one that belongs to root and click X on the top left to close it.
At that point I immediately stopped getting 403 errors and everything started working as expected. Weird thing is i didn’t even have to restart apache it just worked, i guess it restarted itself when i went to my localhost, I honestly don’t know but I guess the problem is Apache not actually restarting when using apachectl restart, or stop or start. Hope this helps someone.
answered Jan 15 ’15 at 22:24
After hours of wasted time this is what solved my issues too. ever.wakeful Feb 7 ’15 at 5:07
If you tail the error log and reload the page, you should see some more information as to the exact problem.
Grab the environment variables so $
Then tail and watch.
I got resolved my self after spending couple of hours.
I installed Apache/2.4.7 (Ubuntu) through coookbook in vagrant vm.
/etc/apache2/apache2.conf file does not have VirtualHost *:80 element by default.
I did two changes to get it done
- added VirtualHost *:80
Options Indexes FollowSymLinks
Allow from all
then finally I just booted vm.
This was driving me crazy. Finally figured out what the problem was: I was using direct paths for the error log and they were wrong.
Why does Apache give a vague (and wrong) error message? Instead use a correct and useful error message like: Path for ErrorLog directive “/wrong/path/and/filename.log” is invalid.
Anyway, to fix make sure your error log directives look something like this: