Fix "508 Resource Limit Is Reached" on CloudLinux hosting

CloudLinux gives every cPanel account its own slice of CPU, memory and processes, so one busy site cannot slow down the whole server. When a site needs more than its slice, visitors see 508 Resource Limit Is Reached. The error is temporary, but it comes back until you remove the cause.

Before you start

• cPanel access to the affected account. Resellers can open it from WHM (see opening a customer cPanel).
• The approximate time the error appeared.

Which limit causes 508?

A 508 almost always means the account hit EP (entry processes: simultaneous PHP requests) or NPROC (total processes). High CPU or IO usage usually makes the site slow rather than showing 508, and a PMEM fault often shows as a 500 or 503 error. The full list is in CloudLinux resource limits explained.

Find the limit that was hit

1. Log in to cPanel.
2. Go to cPanel → Metrics → Resource Usage.
3. The summary says whether the account hit limits in the last 24 hours. Click Details.
4. Choose a period (today, last 7 days) and look at the graphs. Red lines show the limit; spikes that reach it are faults.
5. Scroll to the table and look for non-zero values in the fault columns (EPf, NPROCf, PMemF, CPUf, IOf).

More on reading these graphs is in reading Resource Usage.

Find what is using the resources

• Bot traffic: check cPanel → Metrics → Awstats or the raw access log for hundreds of requests from one IP or crawler. Aggressive SEO bots and fake Googlebots are common culprits.
• Uncached pages: every uncached WordPress page is a PHP process. A busy uncached site hits EP quickly.
• wp-cron and admin-ajax: plugins that poll admin-ajax.php every few seconds keep processes busy.
• Slow database queries: long queries keep PHP processes open, piling up entry processes.
• Attacks: brute-force on wp-login.php or xmlrpc.php.

Fixes that work

1. Turn on caching. MdmHost servers run LiteSpeed, so install LiteSpeed Cache for WordPress (see the LiteSpeed Cache plugin guide). Cached pages are served without PHP and do not count toward EP.
2. Block bad bots. Add rules to .htaccess to block abusive user agents, or ask support to block an IP.
3. Disable WP-Cron on page load. Add define('DISABLE_WP_CRON', true); to wp-config.php and create a real cron job every 15 minutes in cPanel → Advanced → Cron Jobs.
4. Limit login attempts and disable XML-RPC if you do not use it.
5. Remove heavy plugins such as live chat widgets polling the server or stats plugins that log every visit to the database.
6. Upgrade the plan if the site is genuinely busy. A bigger package gives more EP and CPU.

For resellers

You can raise a customer's limits within your plan in CloudLinux Manager (see managing limits in CloudLinux Manager). Raise limits only after caching and bot blocking, otherwise the site just uses the extra room and hits the new limit.

Troubleshooting

508 appears only in wp-admin

The admin area is never cached. Look for plugins running heavy tasks in the dashboard, such as backup or SEO scans.

Resource Usage shows no faults, but you saw a 508

The error page may be cached by a CDN or your browser. Purge the CDN and reload.

Frequently asked questions

Is a 508 error the server's fault?

No. It means the account itself reached its own limit; other sites on the server are unaffected. The fix is on the website side or a bigger plan.

How long does a 508 last?

Only while the account is at the limit. As soon as processes finish, new requests succeed again, often within seconds.

Does more RAM fix entry process faults?

Not directly. EP counts simultaneous requests. Caching and faster pages reduce how many run at once.