On LiteSpeed servers, a 503 Service Unavailable usually means LiteSpeed could not get a working PHP process for the request. The web server itself is fine; something stopped PHP from starting or answering. The causes are few and easy to check.
Before you start
- cPanel access to the affected account.
- The time the error happened and whether it affects all pages or only some.
Check resource limits first
- Go to cPanel → Metrics → Resource Usage.
- Look for memory (PMEM) or process (NPROC) faults at the time of the error.
When the account's memory is full, new PHP processes cannot start and LiteSpeed returns 503. Entry process faults usually show as 508 instead (see 508 errors). Reading the graphs is explained in Resource Usage.
Check the error log
Open cPanel → Metrics → Errors. Messages that point to the cause:
| Message | Meaning |
|---|---|
lsapi: Child process died or Premature end of script headers | PHP crashed during the request |
Allowed memory size exhausted | The script hit memory_limit |
max_execution_time / timeout | A long script was stopped |
PHP Fatal error at startup | A broken extension or syntax error in php.ini |
Fixes by cause
Memory or process limits
- Enable page caching so fewer requests need PHP (see LiteSpeed Cache).
- Remove heavy plugins and stop bots hammering the site.
- Upgrade the plan if the site is genuinely busy.
Crashing extension
In Select PHP Version, untick recently added extensions, or switch PHP version briefly to see whether the 503 disappears (see PHP extensions).
Broken PHP settings
Remove custom php.ini, .user.ini or php_value lines added recently, then test.
Long-running scripts
Imports, backups and reports can run longer than allowed. Raise max_execution_time moderately, or run heavy tasks from cron (see cron jobs with the right PHP).
Tip: A 503 that appears only during busy hours almost always points to limits. A 503 on every request points to PHP configuration.
When to contact support
If Resource Usage shows no faults and the error log has no PHP errors, open a ticket with the URL and time. MdmHost can check the server's LiteSpeed logs.
How LiteSpeed runs PHP is explained in LSAPI explained.
Frequently asked questions
Is a 503 the same as the site being down?
Visitors see an error, but the server is up. Once PHP can start again, the site recovers on its own.
Can a CDN cause a 503?
Yes, CDNs show their own 503 pages when they cannot reach the origin. Check the response headers to see who sent the error.
Why does the error page mention LiteSpeed?
LiteSpeed generates the 503 page when PHP is unavailable. It does not mean LiteSpeed is broken.
Can too many cron jobs cause 503s?
Yes. Cron jobs use the same process and memory limits as the website, so heavy cron jobs during busy hours can starve web requests.