50 articles
Knowledge Base
Troubleshooting
50 articles in the Troubleshooting category · page 1 of 3.
- Account audit on cPanel takeover: what was the previous admin doing? Inheriting a cPanel server means accepting whatever the last admin left behind. A two-hour audit before the first ticket lands tells you what you signed up for.
- Account restore failed with "no such backup": recovery paths A "no such backup" failure during cPanel restore has three causes — wrong path, corrupted index, or a backup that was never written. Each one has a different recovery.
- Building a support escalation matrix: in-house, reseller, cPanel When something breaks at 02:00, the question is not "who knows the answer" but "who can act". A written escalation matrix turns that question into a phone number.
- Cleaning up the old cPanel server after a migration The source server should stay alive in read-only mode for a week, then be retired methodically. Skipping the cleanup costs both money and security.
- Correlating logs across mail, web, and database during a cPanel incident A single-symptom incident usually has evidence in three or four logs. Lining them up by timestamp shows the chain of events the user did not see.
- cPanel DNS cluster sync issues during a multi-server migration A DNS cluster keeps zones synchronized across cPanel hosts. When a migration breaks the sync, mail and web routing go inconsistent. Here is the diagnosis and the fix.
- cPanel license check and fix runbook A cPanel license can fail to validate for half a dozen reasons. The check-and-fix runbook gets through them in five minutes, before the WHM UI locks out.
- cPanel to cPanel transfer with a version mismatch: what works, what does not WHM can transfer between cPanel versions but only in one direction and only across a narrow gap. Here is the matrix that decides whether to upgrade first.
- Customer communications during a cPanel migration: what to send when Most migration complaints are not about the migration. They are about the silence. Here is the communication cadence that prevents the call you do not want.
- Cutover day runbook for a cPanel migration The day of the cutover is hour-by-hour, not improvised. Here is the runbook that makes the difference between a 90-minute cutover and a half-day cutover.
- DirectAdmin to cPanel migration: shape and gaps to watch Moving from DirectAdmin to cPanel/WHM lands cleanly when you know which DirectAdmin features map to cPanel one-to-one and which require manual setup.
- Disaster recovery when you lose the whole cPanel host Losing the entire cPanel host is recoverable if backups exist and you know the order to restore in. The order matters more than people realize.
- Disk-bound vs CPU-bound vs IO-bound triage on a cPanel server A slow cPanel server is one of three things. Distinguishing them takes three commands. The fix is different for each.
- Documenting an inherited cPanel server: the essential captures The handover document for a cPanel server is short — about one page — but it covers the things that take hours to rediscover. Here is what belongs in it.
- Email migration when the MX cannot change for hours When the MX record is owned by a third party that responds in days, mail migration becomes a relay-and-collect exercise — not a flip.
- HTTP 500 Internal Server Error on cPanel: where to look first A 500 on cPanel is almost always a PHP-level problem visible in two specific log files. The trick is reading them in the right order.
- HTTP 502 Bad Gateway on cPanel when LiteSpeed or PHP-FPM is the culprit A 502 on cPanel means the proxy front-end could not get an answer from the upstream — usually LiteSpeed or PHP-FPM. Here is the order of checks.
- HTTP 503 Service Unavailable on cPanel: LVE limits and suspended accounts A 503 on cPanel is usually one of three things: CloudLinux LVE killed the request, the account is suspended, or the web server is throttling.
- HTTP 504 Gateway Timeout on cPanel: long PHP, mod_proxy, upstream A 504 on cPanel means the upstream took longer to respond than the front-end was willing to wait. The fix lives in three timeout settings, not the application.
- HTTP 507 Insufficient Storage on cPanel: quota exhaustion paths A 507 on cPanel is almost always a quota that filled up. There are three quotas worth checking, and the fix is different for each.
- HTTP 508 Loop Detected on cPanel: vhost or .htaccess infinite redirect A 508 on cPanel almost always means a redirect loop in .htaccess or a vhost include that bounces between two URLs forever.
- HTTP 522 from Cloudflare to a cPanel origin: where the path breaks A 522 means Cloudflare could not connect to your cPanel server in time. The fix lives in the firewall, the listener, or the path between Cloudflare and the origin.
- HTTP 525 and 526 from Cloudflare: SSL handshake to cPanel origin A 525 or 526 from Cloudflare means TLS to your cPanel origin failed — wrong cert, expired cert, or the wrong SSL mode in the dashboard. Each one has a specific cause.
- Inheriting an undocumented cPanel server: a week-one runbook The first week of a takeover decides whether you control the server or it controls you. Here is the ordered checklist that turns surprises into known state.