Warning documentroot dev null does not exist httpd

Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. The thing is, the directory absolutely DOES exist. I'm staring right at it. It's not that hard to spell it right. I can't find any other errors or warnings in the httpd logs.

There isn't any symlinks or anything involved here. What am I missing or what else should I look at to determine why this is? The first thing that popped into my mind is does Apache have permission to access that directory? If so, some comparative checking might help. If SELinux is not actively messing with the resource, ls -dZ on the directory will show something like:.

Here is a cut-down man page:. If the web server still cannot see the DocumentRoot, note that the context matters all the way back to root:. Temporary Changes: chcon that states:. With regards to restorecon , note that -F is required to affect the whole context i. Also, -R means to make changes recursively. Arguments -v or -p can show progress in either a verbose or terse fashion. Use -FRnv to see what would happen without actually making any changes. Once semanage is used in this way, it is possible to view local security changes with a command like:.

The output of semanage export may be saved and used by semanage import to make it easier to apply a set of changes to various systems. NOTE: This answer provides a most basic type context for a site. Security can be much more granular. For example, see a list of types that can apply to web server pages with a command like:. NOTE: Utilities like semanage and seinfo may not be installed by default.

At least on some distributions, required packages may be named something like this:. It sounds like SELinux. I would suggest you work with it. Worse case, you can always turn off selinux, as noted earlier, but I suggest you work with it instead. For instance, if I were to create a directory for use with Apache, it will not have the right context, as noted here. So if that happens, I just apply the context from another directory, which in this case, is html:. Sign up to join this community.

The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Apache says DocumentRoot doesn't exist when it does Ask Question. Asked 10 years, 5 months ago. Active 3 years, 5 months ago. Permissions are for Git and its subfolders and files and in my hosts Yes, document root can not be a file such as index.

Use below command to know where is the apache configure file is: then to update the document root:. How are we doing? Please help us improve Stack Overflow. Take our short survey. 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.

Asked 7 years, 9 months ago. Active 7 months ago. Viewed 26k times. I need some help figuring why apache tells me that my document root does not exists. It is there! LouieV LouieV 2 2 gold badges 13 13 silver badges 27 27 bronze badges. Add a comment. Active Oldest Votes.

Your document root cannot be a file, it must be a directory.