Guides › HTML / PHP sites › Site down or error screens

Apache Error: Client Denied by Server Configuration

Access rules.

Reference guide. This guide is written from established practice and the official documentation of the tools involved. We have not yet tested every step on a live demo site. Back up your site before you change anything.
Site down or error page

The error client denied by server configuration appears in the Apache error log when an access rule blocks a request. Visitors see a 403 Forbidden page. The log line names the path, which tells you where to look.

1Read the log line2Check .htaccess in that folder and above3Use Apache 2.4 syntax4Check the server configuration5Check permissions6Check security tools7Reload and retestFixed? Test the site. If not, get help.
The steps in order. Work down the list and stop when the problem is solved.

Step 1: Read the log line

Illustration for Step 1: Read the log line

In your hosting panel open Errors or Logs. The line looks like AH01630: client denied by server configuration: /home/user/public_html/folder. Note the path at the end.

Step 2: Check .htaccess in that folder and above

Illustration for Step 2: Check .htaccess in that folder and above

Open File Manager, enable hidden files and read each .htaccess from the folder up to the site root. Look for Deny from all, Require all denied or an IP allow list that does not include you.

Step 3: Use Apache 2.4 syntax

Illustration for Step 3: Use Apache 2.4 syntax

Older rules such as Order allow,deny with Allow from all can fail on Apache 2.4. Replace them with Require all granted.

Step 4: Check the server configuration

Illustration for Step 4: Check the server configuration

On your own server, a <Directory> block in the Apache config may deny access. Make sure the site's folder has Require all granted, then run apachectl configtest and reload.

Step 5: Check permissions

Illustration for Step 5: Check permissions

Folders should be 755 and files 644, and owned by the site's user.

Step 6: Check security tools

Illustration for Step 6: Check security tools

ModSecurity, a security plugin or a country block can also produce a 403. Check their logs for your IP and the rule that matched.

Step 7: Reload and retest

Illustration for Step 7: Reload and retest

Hard refresh in a private window and confirm the page opens and the log stays quiet.

Still stuck?

If these steps do not solve it, we fix it for you for a flat $99. Full refund if we do not solve it within 7 days.

Related guides

Did this solve it? If not, email hello@sitefixlab.org with the exact error text and we will look into it. Try the problem finder.

Last updated 2026-11-22.