{"id":307,"date":"2026-09-29T10:06:04","date_gmt":"2026-09-29T17:06:04","guid":{"rendered":"https:\/\/hostandtech.com\/kb\/?p=307"},"modified":"2026-09-29T10:06:04","modified_gmt":"2026-09-29T17:06:04","slug":"fix-508-resource-limit-is-reached-cpanel","status":"publish","type":"post","link":"https:\/\/hostandtech.com\/kb\/shared\/fix-508-resource-limit-is-reached-cpanel\/","title":{"rendered":"508 Resource Limit Is Reached: How to Find and Fix the Cause in cPanel"},"content":{"rendered":"

Overview<\/h2>\n

“508 Resource Limit Is Reached” means your hosting account hit one of its CloudLinux limits for a moment and the server refused new requests instead of slowing everyone else down. The fix depends on which limit it was, and cPanel tells you: open Metrics > Resource Usage<\/strong>, look at the fault counts, and deal with that one limit only.<\/p>\n

This guide is for shared and reseller hosting customers who see the 508 page, or a plain 503, on a site that mostly works. You’ll be able to name the limit that faulted, find the request or script behind it, and decide whether a code fix, a cache or a bigger plan is the right answer. Some servers show a 503 instead of a 508 for the same event, so treat both the same way.<\/p>\n

What causes the 508 Resource Limit Is Reached error<\/h2>\n

CloudLinux puts every cPanel account in its own container (an LVE) with fixed ceilings. A 508 is logged as a fault<\/em> against one of these:<\/p>\n\n\n\n\n\n\n\n\n\n
Limit<\/th>\nWhat it caps<\/th>\nUsual culprit<\/th>\n<\/tr>\n<\/thead>\n
EP (entry processes)<\/td>\nSimultaneous requests entering PHP or CGI<\/td>\nSlow pages, bots, admin-ajax storms<\/td>\n<\/tr>\n
CPU<\/td>\nProcessor time, where 100% is one core<\/td>\nHeavy plugins, unindexed queries, crawlers<\/td>\n<\/tr>\n
Memory (PMEM)<\/td>\nRAM for all your processes<\/td>\nImport jobs, page builders, leaks<\/td>\n<\/tr>\n
IO and IOPS<\/td>\nDisk speed and operations<\/td>\nBackups, big logs, uncached reads<\/td>\n<\/tr>\n
NPROC<\/td>\nNumber of processes<\/td>\nStuck cron jobs, runaway scripts<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

EP is the most common by far, because it counts requests waiting at the same moment. A page that takes 4 seconds to build lets only a few visitors per second in before the limit is full, even if the site is small.<\/p>\n

How to fix the 508 error<\/h2>\n

Fix 1: Find out which limit faulted<\/h3>\n
    \n
  1. Log in to cPanel and open Resource Usage<\/strong> in the Metrics<\/strong> section.<\/li>\n
  2. On the Current Usage<\/strong> tab, pick a timeframe that covers the outage. Graphs show your average usage in green and the plan limit in red, with fault markers where you crossed it.<\/li>\n
  3. In the hourly table, the F (Faults)<\/strong> column counts how many times each limit was exceeded in that hour. The resource with faults is your cause.<\/li>\n
  4. Open the Snapshots<\/strong> tab. Each fault saves the running processes, the HTTP requests and the MySQL queries at that moment, which is usually enough to name the guilty script or URL.<\/li>\n<\/ol>\n
    \"Diagram
    Where to find fault counts and snapshots in cPanel Resource Usage.<\/figcaption><\/figure>\n

    Do this before changing anything. Raising an entry process limit does nothing for an account that is CPU bound, and it is the first thing most people ask their host for.<\/p>\n

    Fix 2: Entry processes (EP) faults<\/h3>\n

    Make each request finish faster, so fewer are open at once. Turn on full page caching (LiteSpeed Cache on LiteSpeed servers, or your caching plugin’s page cache elsewhere). Then check for a request flood. With SSH access, this lists the busiest URLs in your access log:<\/p>\n