How to Fix a 500 Internal Server Error
A 500 error is the server's way of saying "something failed but I cannot say what on the page". The error log tells you the real cause; here is the checklist.
Step-by-step
- Read the error log first. cPanel → Metrics → Errors (see error logs) — it almost always names the exact problem.
- Check .htaccess. A bad rule is a top cause — rename .htaccess to .htaccess-off in File Manager; if the site returns, the file had a faulty rule (regenerate it, e.g. resave WordPress permalinks). See editing .htaccess.
- Check file permissions. Files should be 644 and folders 755 — see file permissions. 777 can actually trigger 500 errors.
- Raise PHP limits. Exhausted memory or a timeout shows as a 500 — increase memory and max_execution_time.
- Disable the last change. If it broke after a plugin/theme update, deactivate it (via phpMyAdmin if locked out).
- Still stuck? Note the exact log line and contact EconomicalHost support with it.
💡 Good to know
- The error log is the single most useful tool for a 500 — always start there.
- Never set files or folders to 777; it is both a security risk and a common 500 cause.
- Back up before editing .htaccess or config files.