500 Internal Server Error in cPanel
A 500 Internal Server Error in cPanel means the server accepted the request and then failed. Read the newest line under Metrics › Errors, then make the one change it points to: rename a bad .htaccess, set files to 644 and folders to 755, raise PHP memory or roll back the PHP version. Reload the same URL to confirm.
For site owners and developers on cPanel hosting who need to trace a 500 error from the log instead of guessing.
knowledge
- Read time
- 4 min
- Sections
- 7
- Updated
- 14 Nov 2026
- Written by
- WebJi® team
Last editorial update: 14 November 2026.
What does a 500 Internal Server Error mean on a cPanel account?
A 500 Internal Server Error means the server accepted the request and then failed before it could send a page, almost always because of a file, a PHP limit or a server rule on that account. Changing nameservers will not clear it: the browser has already reached your hosting, so DNS is not the fault.
- 500: the request started and the script or rule crashed.
- 404: no file or route at that address. 503: the service or account is refusing work for now.
- Same error, different wording: Apache's "Internal Server Error" page and LiteSpeed's version are both HTTP 500.
Where do you read the error log in cPanel?
Open cPanel, go to Metrics › Errors and read the newest line for your domain; it names the file and the reason. Also turn on Show Hidden Files in File Manager and open any error_log in the same folder as the broken page.
If both are empty, reload the failing URL once and read again; the new line belongs to that request. If cPanel itself returns 500, or every domain on the account fails and Errors never updates, stop editing files: the server is the suspect, and support needs to look. The difference between web-server and PHP logs is explained in Apache log files explained.
How do you fix a 500 error in cPanel step by step?
Make one change based on the log line, reload the same URL, and stop as soon as it loads. Guessing several fixes at once hides which one worked.
- Copy the newest line from Metrics › Errors: file path and reason.
- Line mentions .htaccess: rename
public_html/.htaccessto.htaccess.bakand reload. If the page returns, restore rules one block at a time. - "Allowed memory size … exhausted": in Software › MultiPHP INI Editor, select the domain and set memory_limit above the figure in the log, as in increasing the PHP memory limit.
- Permissions or "writeable by group": set files to 644 and folders to 755. Never 777.
- "Call to undefined function" or a syntax error after a PHP change: switch the domain's version in Software › MultiPHP Manager back to the one the code supports, then update the code (see changing the PHP version in cPanel).
- Path under wp-content: go to the WordPress section below.
- Reload. It is fixed when the page loads and Errors shows no new line for that request.
What do common 500 error log lines mean?
Each log phrase points at one change; match it, make that change and reload. If your phrase is not listed, email the whole line instead of guessing.
| Log phrase | Likely cause | Change this |
|---|---|---|
| Invalid command '…', perhaps misspelled | A directive the server does not support, e.g. php_value on PHP-FPM | Remove that line from .htaccess |
| Request exceeded the limit of 10 internal redirects | Redirect loop in rewrite rules | Rename .htaccess; rebuild rules one block at a time |
| Allowed memory size of … bytes exhausted | PHP memory limit too low for the task | Raise memory_limit for the domain |
| SoftException … is writeable by group/others | A file or folder set to 775 or 777 | Set 644 for files, 755 for folders |
| Premature end of script headers | The script died before any output | Open the PHP file named in the line |
| Primary script unknown / No input file specified | The path is not a real PHP file | Fix the path or upload the missing file |
What if the 500 error log points at WordPress?
If the path sits under wp-content, the hosting checks are done and the fault is a plugin or theme; continue with the WordPress 500 error guide. Copy the log line before renaming any plugin folder, so you know which one to blame.
A 500 that appears only in webmail while the website loads belongs to the panel's mail application, not to public_html. Do not wipe .htaccess to chase it; send that log line to support instead.
When is the server itself the cause of a 500 error?
Suspect the server only when cPanel itself fails, every account's sites return 500, or the log names a service you cannot restart. On shared hosting, CPU or process limits usually show as 503 or 508 rather than 500.
Moving to a bigger plan does not repair one bad file. Upgrade only when support confirms the machine or your resource limits are the bottleneck; WebJi® cPanel VPS servers and dedicated servers are quoted by email before payment.
What should you send support about a 500 error?
Send the domain, the time of the failure, the newest log line and what you already changed. That lets the desk start at the right layer instead of asking the same questions.
Email support@webji.services; support is 24/7 by email in Hindi and English, with an average first reply under 60 minutes. Customers on WebJi® cPanel hosting can also mention whether the error started after a plugin update, a PHP version change or a migration.
Frequently asked questions
Why did a 500 error start right after I edited .htaccess?
Most likely a typo or a directive the server does not support, such as php_value on a PHP-FPM server. Undo the last edit or rename the file to .htaccess.bak, reload, and add the change back with the correct syntax for your server.
Can a PHP version change cause a 500 error?
Yes. Older plugins and scripts can call functions removed in PHP 8, which causes a fatal error. Switch the domain back in MultiPHP Manager to restore the site, then update the code before trying the newer version again.
Does a 500 error affect Google rankings?
A short outage rarely matters, because Google retries later. Errors lasting days can cause pages to drop from the index. Fix the cause, then check Search Console's Pages report for server errors and request recrawling of key URLs.
Why is the cPanel Errors page empty?
It shows recent web-server errors only. If nothing appears after reloading the failing URL, the error may come from a CDN or proxy in front of the site, or from a PHP log written elsewhere. Check error_log files in the site folders and the domain's PHP log path.
Last editorial update: 15 November 2026.
Ready to get started with WebJi®?
Join 12,000+ businesses across India and overseas. INR pricing, 18% GST shown before payment and 24/7 email support in Hindi and English — average first reply under 60 minutes.