Fixing 403, 404, and 500 Errors

Fixing 403, 404, and 500 Errors: Common File and Folder Causes in cPanel

If your website suddenly displays an error like 403 Forbidden, 404 Not Found, or 500 Internal Server Error, the cause is often related to files, folders, permissions, redirects, or a corrupted .htaccess file. Not every error means the entire website is broken. Often, a targeted check in the cPanel File Manager is sufficient.

This article explains the most common file and folder causes of these error messages and shows you how to systematically check what happened.

403 Forbidden: Access Denied

A 403 Forbidden error means that the server understood the request but refuses to grant access. In the context of files and folders, permissions, missing startup files, or access protection rules are frequently responsible.

Common Causes

• Incorrect file permissions,
• Incorrect folder permissions,
• No index.php or index.html in the directory,
• Directory listing is disabled,
• .htaccess rules are blocking access,
• Directory protection is active,
• IP address has been blocked.

Checking in cPanel

1. Open the File Manager.
2. Navigate to the affected folder.
3. Check if a startup file like index.php or index.html exists.
4. Check the permissions: usually 755 for folders and 644 for files.
5. Enable hidden files and check the .htaccess file.
6. Check if directory protection is active.

404 Not Found: File or Page Not Found

A 404 Not Found error means that the server could not find the requested file or URL. This can happen if files have been deleted, moved, or renamed, or if redirects and permalinks are not functioning correctly.

Common Causes

• File was deleted or moved,
• File name or path is incorrect,
• Case sensitivity does not match,
• ZIP file was extracted into an additional subfolder,
• Incorrect document root for the domain,
• Faulty redirect,
• For WordPress: Permalinks or .htaccess rules are corrupted.

Checking in cPanel

1. Check in the File Manager to see if the file actually exists.
2. Compare the file name, extension, and case sensitivity.
3. Check if the file is in the correct web directory.
4. Check the .htaccess file for redirects or rewrite rules.
5. For WordPress: Resave the permalink structure in the admin area.

500 Internal Server Error: Server Error

A 500 Internal Server Error is a generic error message. The server was unable to successfully process the request. In a file context, faulty .htaccess rules, PHP errors, incorrect permissions, or broken scripts are often responsible.

Common Causes

• Syntax error in the .htaccess file,
• Unsupported Apache directive,
• PHP error in a file,
• Broken plugin or theme,
• Incorrect file permissions,
• Exhausted storage space,
• Faulty redirect loop.

Quick Test if .htaccess is Suspected

1. Open the File Manager.
2. Enable hidden files.
3. Locate the .htaccess file in the affected directory.
4. Rename it as a test, for example to .htaccess-test.
5. Try accessing the website again.
6. If the website works again, the error is likely within the .htaccess file.

For WordPress, you can then resave the permalink structure in the admin area under Settings > Permalinks, so that WordPress recreates the required rules.

Checking Error Logs

If the cause is not obvious, error logs can help. There are often files named error_log in the affected directory or in subfolders.

1. Open the File Manager.
2. Search for error_log.
3. Open the file if it is not too large.
4. Check the most recent entries.
5. Look for file paths, plugin names, theme names, or PHP error messages.

If an error_log file is very large, it can also cause storage space issues. It can generally be deleted, but it will be recreated if the error persists.

Quick Overview

Safe Diagnostic Workflow

1. Note when the error first started occurring.
2. Check if files were modified, deleted, or uploaded shortly before.
3. Check the affected folder in the File Manager.
4. Verify startup files, file paths, and permissions.
5. Enable hidden files and check the .htaccess file.
6. Check error_log files.
7. If necessary, restore a backup.

When Should a Backup be Used?

If a file was accidentally deleted or a configuration was corrupted, restoring from a backup can be useful. Especially in the following cases:

• .htaccess was incorrectly modified,
• index.php was overwritten,
• A theme or plugin folder was corrupted,
• Files were accidentally deleted,
• The website stops working after an upload.

If possible, restore only the specific affected file or folder rather than the entire account unnecessarily.

Best Practices for Prevention

• Always create a backup copy before making changes.
• Modify .htaccess rules only step-by-step.
• Upload files to the correct document root.
• Ensure correct startup files are in place.
• Avoid insecure permissions such as 777.
• Do not delete unknown system or CMS files.
• Check the website in your browser after every upload.