Troubleshoot 403, 404, 500 and resource-limit errors Print

0

Start with the exact status code and time. Random changes often hide the real cause and make recovery harder.

Steps

Test in a private window and another network. Confirm the domain resolves correctly and the hosting service is Active.
Open cPanel → Metrics → Errors and Resource Usage. Match entries to the failure time; also check disk and inode usage.
For 404, verify the document root, filename and rewrite rules. For 403, check permissions and security rules. For 500, review PHP errors, .htaccess and the most recent code change.
Temporarily disable only the suspected plugin, rule or change. Do not rename or delete the whole site. Restore a known-good backup if the failure followed an update.
If limits are repeatedly reached, reduce abusive traffic, optimize the application and scheduled jobs, then contact support with the URL, UTC time, code and error-log excerpt.

Verify the result

The page should work repeatedly while Errors and Resource Usage remain clear. Re-enable components one at a time to prove the cause.

Important: Do not paste passwords, full configuration files or customer data into a support ticket. Redact secrets from logs.

Was this answer helpful?

Related Articles

Your first cPanel setup checklist Complete these checks before publishing a new site. They prevent the most common domain, security... Upload and publish website files with File Manager or SFTP The document root is the folder served for a domain. Uploading to the wrong folder is the most... Change the PHP version and upload limits safely Use cPanel’s supported PHP tools instead of copying old php.ini examples from another server.... Create and verify a cPanel backup before changes A backup is useful only when it contains the needed files and database and can be found after an...

« Back