How to Fix HTTP Errors in Plesk / cPanel
Plesk and cPanel servers expose HTTP errors through their own log interfaces and configuration panels. Distinct from raw Apache/nginx debugging. This guide covers panel-managed-server HTTP error troubleshooting. Pair with HTTP error audit guide.
Step-by-step: How to fix HTTP errors in Plesk / cPanel
- Access error logs. Plesk: Domain → Logs → error_log. cPanel: Errors section in cPanel home, or Metrics → Errors. Latest entries at top. Filter by time range when investigating a specific incident.
- Identify error pattern. 500 = server error (often PHP fatal error or .htaccess issue). 502 = bad gateway (upstream like PHP-FPM not responding). 503 = service unavailable (overload or maintenance mode). 504 = gateway timeout (slow upstream). 403 = forbidden (permission or .htaccess deny). 404 = not found (file missing or rewrite rule wrong). Each error type points to different fixes.
- Check PHP error log. Plesk: Tools & Settings → PHP Settings → error_log path. Common location: /var/www/vhosts/yoursite.com/logs/error_log. Fatal errors, timeouts, memory limit exceeded all logged here. Many 500 errors trace to PHP.
- Verify resource limits. Plesk: Subscription → Hosting Settings → resource limits. PHP memory_limit, max_execution_time, max_input_vars. cPanel: PHP Selector. Inadequate limits cause 500/502 errors under load.
- Check .htaccess. Bad RewriteRule patterns cause 500. Test by renaming .htaccess temporarily — if 500 disappears, the file is the issue. Iterate: remove sections until error stops, restoring lines until error returns. Identifies the offending rule.
- Fix 502/503 patterns. 502 often: PHP-FPM down (restart via Plesk → Services or cPanel WHM → Services). 503 often: server overloaded, traffic spike. Check load average: 'top' or 'uptime'. Above core count = overloaded.
- Set up monitoring. Plesk: Statistics → HTTP errors. cPanel: Cron job grepping recent errors. External monitoring (UptimeRobot, StatusCake) catches errors users see but you might miss in logs. Email/Slack alerts on 5xx spikes.
🟢 Audit Plesk/cPanel HTTP errors
Get an audit of HTTP errors on your managed server.
Run HTTP Error Audit →Frequently Asked Questions
How do I find the correct error log on Plesk?
Plesk: Domain → Logs → error_log shows recent entries. For raw access: SSH to server, cd /var/www/vhosts/yoursite.com/logs/ — files: error_log (Apache/nginx errors), php_error_log (PHP fatal/notice). Plesk Onyx (v17+) and Obsidian (v18+) UI provides tail and search in browser.
Why are 502 errors common on Plesk under traffic spikes?
Plesk runs Apache + nginx (nginx as reverse proxy in front of Apache by default). When Apache or PHP-FPM workers exhaust, nginx returns 502. Increase: Plesk → Domain → Apache & nginx Settings → PHP-FPM pool size (max_children, max_requests). Or upgrade PHP-FPM to nginx-only mode for higher throughput.
cPanel vs Plesk for SEO error handling?
Functionally similar. Both expose error logs, both manage PHP/Apache/nginx configs. cPanel slightly more common at shared hosting (Bluehost, HostGator, GoDaddy use cPanel). Plesk more common at VPS/dedicated (1&1, Liquid Web). SEO-wise no difference; both can be misconfigured.
How do I handle 404 errors on Plesk-hosted WordPress sites?
WordPress 404s: usually permalink configuration. Settings → Permalinks → save (refreshes rewrite rules). Verify .htaccess (or nginx config on Plesk nginx-only) contains WordPress rules. If 404s persist, check file permissions: WordPress files should be 644, directories 755.
Best tools to monitor HTTP errors on Plesk/cPanel?
Plesk Statistics — built-in error tracking. cPanel Awstats / Webalizer — basic log stats. External: Datadog, New Relic, Pingdom for production monitoring. Free: UptimeRobot, StatusCake. Most production sites need external monitoring (panel stats are aggregated, not real-time).