CloudLinux Resource Limit: causes and fixes
The Resource Limit Is Reached (508) error means your account has hit a CloudLinux CPU, RAM, or Entry Process limit.
UnderHost NOC
Network Operations
The "Resource Limit Is Reached" error (HTTP 508) means your hosting account has exceeded a resource limit enforced by CloudLinux. Your site is not permanently down-the account is throttled or paused while usage drops back within the allowed threshold, then resumes automatically.
What the error means
CloudLinux assigns each shared hosting account its own resource container (LVE) with limits on CPU, RAM, simultaneous PHP processes (Entry Processes), and disk I/O. When any limit is reached, visitors to your site see an error until usage falls back below the threshold.
| Error / symptom | Most likely cause |
|---|---|
| 508 Resource Limit Is Reached | Too many simultaneous PHP requests (Entry Process limit) |
| 500 Internal Server Error | PHP process killed by RAM limit |
| Very slow pages, no error displayed | CPU throttling |
| Cannot upload files / email bounces | Disk space or inode limit |
Common causes
- Traffic spike-a sudden surge in visitors causes many simultaneous PHP requests
- No page caching-every visitor triggers a full PHP execution; without caching, even moderate traffic can hit Entry Process limits
- Runaway plugin or script-one misbehaving plugin or scheduled task continuously consumes CPU
- Heavy database queries-complex WooCommerce queries or unindexed database tables
- Cron job accumulation-wp-cron firing too frequently or overlapping with itself
- Malware-compromised account files running scripts silently in the background
How to check your usage
- Log in to cPanel
- Go to Metrics → Resource Usage
- Check the Current Usage tab for live readings
- Check the History tab to see when and which resource spiked
- Look for any resource at or near 100%-that is your bottleneck
See the Resource Usage plugin guide for a full explanation of each metric and graph.
How to fix it
1. Enable page caching
For WordPress, install a caching plugin (WP Super Cache, W3 Total Cache, or LiteSpeed Cache). This is the single most effective fix for Entry Process (508) errors-cached pages are served as static HTML without running PHP, so they cost zero Entry Processes.
2. Identify the heavy process
In cPanel, go to Metrics → CPU and Concurrent Connection Usage to see which scripts are active. Check the Errors log under Metrics for PHP fatal errors related to memory limits.
3. Disable plugins one at a time
Deactivate all WordPress plugins, then reactivate them one at a time while watching Resource Usage. When the spike returns, that's the problem plugin.
4. Optimize your database
Use phpMyAdmin → Optimize Table on large tables, or use WP-Optimize to remove auto-drafts, spam comments, expired transients, and post revisions.
5. Check for malware
Use cPanel's Virus Scanner or open a support ticket to request a malware scan. Hidden scripts from compromised accounts are a common cause of persistent CPU overuse.
The 508 error appears and resolves on its own as resource usage fluctuates. If it's happening constantly throughout the day, your site has a structural issue-caching or optimization is needed.
When to upgrade to a VPS
If you've optimized your site and are still consistently hitting limits, your site has genuinely outgrown shared hosting. A Cloud VPS provides fully dedicated CPU and RAM-no LVE limits, no throttling, and no competition with other accounts. Contact UnderHost support to find the right VPS plan for your traffic.
Related: Resource limits | CloudLinux overview | CloudLinux resource usage | Shared hosting overview
Need shared hosting?
Choose an UnderHost shared hosting plan with cPanel, email, SSL, DNS tools, and 24/7 support.
