Nginx forbidden files

I tried every answer above, nothing worked. What fixed it for me though was removing the domain, and adding it again. We had the same issue, using Plesk Onyx Instead of messing up with rights etc. Now nginx has rights to access. And don't forget to restart both Apache and Nginx in Plesk after! So, after lot of struggle I found out that sestatus was set to enforce which blocks all the ports and by setting it to permissive all the issues were resolved.

I dug myself into a slight variant on this problem by mistakenly running the setfacl command. I ran:. I abandoned this route in favor of adding nginx to the foo group, but that custom ACL was foiling nginx's attempts to access the file. I cleared it by running:. For more info checkout the index directive in the official documentation.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Nginx forbidden for all files Ask Question. Asked 10 years, 5 months ago. Active 1 year ago. Viewed k times. XX, server: www. Have I done something silly here? Angus Ireland Angus Ireland 2, 3 3 gold badges 23 23 silver badges 19 19 bronze badges.

Add a comment. Active Oldest Votes. Same here. Can someone explain why this behavior is different than apache which does NOT require every parent directory to have "x" permissions?!? To allow nginx to serve your www directory make sure you turn SELinux back on before testing this. See my answer here for more details. The issue is caused when you mv something from one place to another. Running restorecon puts the context back to its default and fixes it too.

Old question, but I had the same issue. I tried every answer above, nothing worked. Enable this module by adding the following entry to the configuration file. For more information on how to serve static content, consider the Nginx documentation resource provided below:. Nginx forbidden error can also result from files and directories having incorrectly set permissions. For Nginx to successfully server a specific file and resource to the client, Nginx needs to have RWX—read, write and execute—permissions on the entire path.

To resolve this error, change the directories permission to and the file permissions to Ensure that the user running the Nginx process owns the files. For example, set user to www-data:. Your email address will not be published. Submit Comment. Or click here to learn more. When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to.

The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.