Post Date: October 12, 2017
Last Updated: September 17, 2026<\/p>\n\n\n\n
While configuring Apache 2.4 on a Linux server, you may encounter the following error in the Apache error log:<\/p>\n\n\n\n
Client denied by server configuration<\/pre>\n\n\n\nThis error generally indicates that Apache is preventing access to the requested directory because the document root has not been explicitly allowed in the Apache configuration.<\/p>\n\n\n\n
For example, if a website uses the following document root:<\/p>\n\n\n\n
\/home\/domain\/public_html<\/pre>\n\n\n\nApache may deny access unless the directory is permitted in the VirtualHost configuration.<\/p>\n\n\n\n
This guide explains how to allow access to the document root and resolve the error.<\/p>\n\n\n\n
Prerequisites<\/h2>\n\n\n\n
Before making the changes, make sure you have:<\/p>\n\n\n\n
For this example, we use:<\/p>\n\n\n\n
\/home\/domain\/public_html<\/pre>\n\n\n\nand assume the Apache VirtualHost configuration is:<\/p>\n\n\n\n
\/etc\/apache2\/sites-enabled\/domain.conf<\/pre>\n\n\n\nUnderstanding the Error<\/h2>\n\n\n\n
The error:<\/p>\n\n\n\n
Client denied by server configuration<\/pre>\n\n\n\nusually occurs when Apache’s access-control rules do not permit access to the directory being requested.<\/p>\n\n\n\n
Apache 2.4 uses the
Require<\/code> directive for access control. Therefore, the document root needs an appropriate<Directory><\/code> configuration.<\/p>\n\n\n\nImplementation<\/h2>\n\n\n\n
Step 1: Open the Apache VirtualHost Configuration<\/h3>\n\n\n\n
Open the VirtualHost configuration file:<\/p>\n\n\n\n
vi \/etc\/apache2\/sites-enabled\/domain.conf<\/pre>\n\n\n\nLocate the existing VirtualHost configuration and add a
<Directory><\/code> block for the website’s document root.<\/p>\n\n\n\nStep 2: Allow Access to the Document Root<\/h3>\n\n\n\n
Add the following configuration:<\/p>\n\n\n\n
<Directory \"\/home\/domain\/public_html\">\n Require all granted\n<\/Directory><\/pre>\n\n\n\nThe complete VirtualHost configuration may look similar to:<\/p>\n\n\n\n
<VirtualHost *:80>\n\n ServerName domain.tld\n ServerAlias www.domain.tld\n DocumentRoot \/home\/domain\/public_html\n\n <Directory \"\/home\/domain\/public_html\">\n Require all granted\n <\/Directory>\n\n<\/VirtualHost><\/pre>\n\n\n\nThe
Require all granted<\/code> directive allows Apache to serve content from the specified directory.<\/p>\n\n\n\nStep 3: Verify the Apache Configuration<\/h2>\n\n\n\n
Before restarting Apache, check the configuration for syntax errors:<\/p>\n\n\n\n
apachectl -t<\/pre>\n\n\n\nIf the configuration is correct, you should see:<\/p>\n\n\n\n
Syntax OK<\/pre>\n\n\n\nIf an error is reported, correct the configuration before applying the changes.<\/p>\n\n\n\n
Step 4: Restart Apache<\/h2>\n\n\n\n
Restart Apache to apply the configuration:<\/p>\n\n\n\n
service apache2 restart<\/pre>\n\n\n\nOn systems using
systemd<\/code>, you can also use:<\/p>\n\n\n\nsystemctl restart apache2<\/pre>\n\n\n\nStep 5: Test the Website<\/h2>\n\n\n\n
Open the website in a browser:<\/p>\n\n\n\n
http:\/\/domain.tld<\/pre>\n\n\n\nIf the
<Directory><\/code> configuration was the cause of the issue, Apache should now be able to serve the website content from:<\/p>\n\n\n\n\/home\/domain\/public_html<\/pre>\n\n\n\nTroubleshooting<\/h2>\n\n\n\n
If the error continues after adding
Require all granted<\/code>, check the following:<\/p>\n\n\n\nCheck the Document Root<\/h3>\n\n\n\n
Make sure the configured
DocumentRoot<\/code> matches the actual website directory:<\/p>\n\n\n\nDocumentRoot \/home\/domain\/public_html<\/pre>\n\n\n\nCheck the Directory Path<\/h3>\n\n\n\n
Make sure the
<Directory><\/code> path matches the document root exactly:<\/p>\n\n\n\n<Directory \"\/home\/domain\/public_html\">\n Require all granted\n<\/Directory><\/pre>\n\n\n\nCheck Apache Configuration<\/h3>\n\n\n\n
Run:<\/p>\n\n\n\n
apachectl -t<\/pre>\n\n\n\nCheck Apache Error Logs<\/h3>\n\n\n\n
Review the Apache error log for additional information:<\/p>\n\n\n\n
tail -f \/var\/log\/apache2\/error.log<\/pre>\n\n\n\nDepending on the VirtualHost configuration, the website may also have its own error log.<\/p>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
The Apache 2.4 error \u201cClient denied by server configuration\u201d<\/strong> commonly occurs when Apache’s access-control configuration does not allow access to the website’s document root.<\/p>\n\n\n\n
Adding an appropriate
<Directory><\/code> block with:<\/p>\n\n\n\n<Directory \"\/home\/domain\/public_html\">\n Require all granted\n<\/Directory><\/pre>\n\n\n\nallows Apache to serve content from the specified document root.<\/p>\n\n\n\n
Always validate the configuration with
apachectl -t<\/code> before restarting Apache.<\/p>\n\n\n\nFrequently Asked Questions<\/h2>\n\n\n\n
1. What does \u201cClient denied by server configuration\u201d mean in Apache?<\/h3>\n\n\n\n
It means Apache’s configuration is preventing the client from accessing the requested resource. One possible cause is that the website’s document root has not been allowed through a suitable
<Directory><\/code> rule.<\/p>\n\n\n\n2. What directive is used to allow access in Apache 2.4?<\/h3>\n\n\n\n
Apache 2.4 uses the
Require<\/code> directive. For example:<\/p>\n\n\n\nRequire all granted<\/pre>\n\n\n\nallows access to the configured directory.<\/p>\n\n\n\n
3. Do I need to restart Apache after changing the configuration?<\/h3>\n\n\n\n
Yes. After validating the configuration, restart or reload Apache so that the changes take effect.<\/p>\n\n\n\n
apachectl -t\nsystemctl restart apache2<\/pre>\n\n\n\n4. Why is the
<Directory><\/code> path important?<\/h3>\n\n\n\nThe
<Directory><\/code> path must match the actual filesystem location of the website’s document root. If the paths do not match, the intended access rule may not apply.<\/p>\n\n\n\n5. Does this error always mean the
<Directory><\/code> directive is missing?<\/h3>\n\n\n\nNo. A missing or restrictive
<Directory><\/code> rule is one common cause. Other Apache access-control rules, filesystem permissions,.htaccess<\/code> settings, or security modules can also result in access being denied.<\/p>\n\n\n\nRelated Articles<\/h2>\n\n\n\n