How to fix the 403 forbidden error: Difference between revisions
Jump to navigation
Jump to search
| Line 60: | Line 60: | ||
Root cause: the original syntax was written for another version of HTTP server. | Root cause: the original syntax was written for another version of HTTP server. | ||
== More detail on HTTP server log == | |||
Log files maybe located on {{ | Log files maybe located on {{kbd | key=<nowiki>/var/log/httpd/</nowiki>}} | ||
== References == | == References == | ||
Revision as of 10:47, 9 December 2024
How to fix the 403 forbidden error
Error message
When I tried to browse the website, I met the following message:
Forbidden You don't have permission to access this resource. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
Troubleshooting process of the 403 forbidden error
Client side: Check the permission
Browser Configuration
- Clear browser cache and cookies
- Enable cookies in browser settings
- Try incognito/private browsing mode
- Disable VPN or proxy services temporarily
- Clear browser's saved credentials for the site
Authentication
- Verify you're logged in correctly
- Check if your account has the necessary permissions
- Try logging out and logging back in
- Ensure your password hasn't expired
Server side: Check the SELinux policy if SELinux was enabled
The result of ls -Zd should contains "httpd_sys_content_t:"
$ ls -Zd /path/to/website/ drwxr-xr-x. apache apache unconfined_u:object_r:httpd_sys_content_t:s0 /path/to/website/
Server side: Check the configuration of HTTP server
Check if home directory exists e.g. /path/to/website/ in the configuration of HTTP server. The folder location of configuration files maybe located on Template:Kdb depends on the HTTP server environment.
<Directory /path/to/website/> .. </Directory>
Server side: Check the syntax of .htaccess
Check if the syntax of .htaccess (/path/to/website/.htaccess ) correct.
Example content of log
/path/to/website/.htaccess: Invalid command 'Force', perhaps misspelled or defined by a module not included in the server configuration, referer: http://mywebsite.com.tw/favicon.ico
Root cause: the original syntax was written for another version of HTTP server.
More detail on HTTP server log
Log files maybe located on /var/log/httpd/