I followed the virtual hosts tutorial and set up apache for my domain name aditidentalcare.com. The website was loading perfectly but now I am suddenly getting this error.
Forbidden - You don’t have permission to access / on this server.
I don’t understand why!
Here is the aditidentalcare.com.conf
<VirtualHost *:80> ServerAdmin jogi@smashingpixels.in ServerName aditidentalcare.com ServerAlias www.aditidentalcare.com DocumentRoot /var/www/html/sites/aditidentalcare.com/public_html ErrorLog /error.log CustomLog /access.log combined </VirtualHost>
The permission for public_html is set to 750 and the owner:group is jogi:www-data
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!
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.
Sign up for Infrastructure as a Newsletter.
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
@joginayak
You need to use
chmod
755 instead of 750 on directories. Using 750 equates to users having read, write, and execute, groups having read and execute, and finally, world (i.e your visitors) having absolutely zero access, thus they will be forbidden from accessing and/or viewing the contents.Hello,
One more thing that I could suggest in addition to what already has been mentioned is that you could also check the user that your Apache service is running as and change the owner of your files:
In most cases, it would be
www-data
unless it was changed.Make sure to change the
www-data
user if this is not the one that your Apache service is running as.Regards, Bobby
@srjcooldude @kasidkhan
if you were using a wordpress site, it could have quite possibly been caused by a corrupt .htaccess file. the simple fix is to resave permalinks twice in order to regenerate .htaccess.
you might be seeing the below error messages:
br, tom