A "Resource Limit Is Reached" or 508 error means that CloudLinux, the security layer running on our shared and reseller hosting servers, has temporarily stopped your website because it exceeded one of its allocated resource limits.
This guide explains what the different limits are, how to identify which one is being hit, and how to resolve it.
What resource limits are in place?
Each shared and reseller hosting account has limits on the following:
| Limit | What it controls | Common cause |
|---|---|---|
| CPU | Processing power your account can use | Heavy PHP scripts, unoptimised database queries, large image processing |
| Memory (RAM) | Memory available per process | Memory-hungry WordPress plugins, large data imports, complex WooCommerce stores |
| Entry Processes (EP) | Number of simultaneous PHP processes your account can run at once | A sudden traffic spike, or a runaway script opening many processes |
| Inodes | Total number of files and folders on your account | Excessive email accumulation, large cache folders, too many backup files stored on the server |
Step 1: Check which limit is being exceeded
- Log in to cPanel.
- Scroll to the Metrics section and click Resource Usage (sometimes labelled CPU and Concurrent Connection Usage).
- Review the usage graphs. Look for any metric that is consistently near or at 100%, that is your culprit.
- Check the Faults column, this shows how many times each limit has been hit, which helps confirm which one is causing the 508 error.
Tip: The graphs show usage over time. If you see spikes at particular times of day, this can point towards a scheduled task (cron job) or a specific period of high traffic as the trigger.
Step 2: Fix the issue based on which limit is being hit
High Entry Processes (EP), most common cause of 508 errors
Entry Processes represent how many PHP scripts are running simultaneously on your account. When this limit is hit, new visitors get the 508 error while existing requests are still being processed.
Common fixes:
- Enable page caching, caching serves pages as static HTML files, dramatically reducing the number of PHP processes needed. For WordPress, install WP Super Cache or LiteSpeed Cache from the WordPress plugin directory.
- Check for runaway scripts, a poorly written plugin or script can loop and hold processes open. Temporarily deactivating plugins one by one (see the WordPress section below) often identifies the cause.
- Review your cron jobs, if a cron job is scheduled to run frequently and takes a long time to execute, it can exhaust Entry Processes. Check your cPanel cron jobs under Advanced → Cron Jobs.
High CPU usage
CPU spikes usually point to inefficient code or database queries running repeatedly.
- WordPress users: SEO plugins, page builder plugins, and backup plugins are frequent CPU offenders, especially if configured to run during peak hours. Check which plugins are active and temporarily deactivate non-essential ones to test.
- Database queries: Slow or un-indexed database queries can consume significant CPU. If you have access to your database, look for queries not using indexes. Contact support if you need help identifying these.
- Schedule intensive tasks for off-peak hours, move backup jobs and any heavy cron tasks to run at 2–4am rather than during the day.
High memory usage
- Identify memory-hungry plugins or scripts. For WordPress, plugins that handle image processing, PDF generation, or large data exports often spike memory usage.
- Check your PHP memory limit is set sensibly. You can view and adjust it in cPanel under Software → Select PHP Version → Options. Note that on shared hosting there is a maximum cap, if you genuinely need more memory consistently, a VPS is the appropriate solution.
High inode count
Inodes are individual files and folders. Each hosting account has a maximum number. Common culprits:
- Email: Every email stored on the server is an inode. Empty your spam and trash folders in webmail, and consider setting up email clients to use IMAP with a shorter retention period for deleted items.
- WordPress cache: Cache plugins can generate thousands of files. Clear your cache folder (
/wp-content/cache/) via FTP or File Manager. - Backups stored on the server: Backups should be downloaded and stored off-server. Delete any old backup archives sitting in your
public_htmlor home directory. - Session files: PHP session files in
/tmpcan accumulate. Contact support if you suspect this is the cause.
To check your current inode count, go to cPanel → Files → Disk Usage and look for the Inode Count figure at the top.
WordPress-specific diagnosis
WordPress is the most common source of resource limit errors on shared hosting due to plugin conflicts, inefficient themes, and misconfigured caching. If your site runs WordPress:
- Deactivate all plugins: Connect via FTP or cPanel File Manager and rename
/wp-content/plugins/to/wp-content/plugins-disabled/. If the 508 error stops, a plugin is the cause. Rename the folder back topluginsand reactivate them one by one to identify which one is responsible. - Check wp-cron: WordPress has a built-in task scheduler (
wp-cron.php) that runs on every page load. On busy sites this can trigger many simultaneous processes. Consider disabling it and running it via a real server cron job instead, see our wp-cron guide. - Install a caching plugin: If you don't already have one, install LiteSpeed Cache or WP Super Cache. Effective caching is the single most impactful change you can make for a resource-heavy WordPress site.
If the error keeps coming back
If you are consistently hitting resource limits despite optimising your site, this is a strong signal that your site has outgrown shared hosting. Our VPS and Cloud hosting plans provide dedicated resources with no shared limits, meaning your site's performance is not affected by other accounts, and you won't hit a 508 ceiling.
Contact our team to discuss which plan would suit your requirements, we can review your current usage and recommend the right option.
