View Plans
Help

How to fix “508 Resource Limit Is Reached”

“508 Resource Limit Is Reached” means your hosting account reached one of its limits, most often the number of requests it can run at once, and the server turned new visits away. It clears on its own once the load drops. To stop it coming back, find what uses the resources, add caching and block bad bots.

Updated · HostUpIndia team

What “508 Resource Limit Is Reached” means

On shared hosting, every account has limits, so one site cannot slow the server for everyone. Nothing is lost when a site reaches one. It comes back once the load drops, usually within minutes.

Reaching the CPU or I/O limit mostly makes the site slow. The 508 page usually means the entry process limit was reached: too many requests at once. Slow pages hold each request longer, so a slow site reaches it sooner.

Seeing “503 Service Unavailable” instead? See how to fix the 503 error.

  • CPU: how much processor time the account can use.
  • Memory: how much RAM all of the account’s processes can use together.
  • Entry processes: how many requests to the site can run at the same time.
  • Number of processes: every process the account runs at once, including PHP, cron jobs and scripts.
  • I/O: how fast the account can read from and write to disk.

Find what causes the 508 error

Common causes are a traffic spike, bots and crawlers, heavy plugins, cron jobs that run every minute, pages served without a cache, and attacks on WordPress’s xmlrpc.php or login page.

  • Note the time the 508 page appeared.
  • Log in to cPanel and look under Metrics for Resource Usage. Not every host provides it. If yours does not, ask support which limit was reached, and when.
  • In Resource Usage, see which limit was reached and at what times.
  • Open Metrics › Visitors and select your domain. It lists recent requests with the IP address, page and user agent.
  • Look for one IP address or bot with far more requests than the rest, and for many requests to xmlrpc.php or wp-login.php.
  • Open Cron Jobs and look for any job set to run every minute.
  • In WordPress, note any plugin added or updated just before the errors began.

Add caching and trim plugins

A cached page is served without running PHP or the database, so it uses a fraction of the resources. On a LiteSpeed server, the free LiteSpeed Cache plugin does this for WordPress.

  • In WordPress, go to Plugins › Add New Plugin and search for LiteSpeed Cache.
  • Install and activate it.
  • Open LiteSpeed Cache › Cache and check that Enable Cache is on.
  • Load a page twice while logged out. In your browser’s developer tools, check that the second response has x-litespeed-cache: hit.
  • Not on a LiteSpeed server? Use a page cache plugin that suits your server. For other apps, turn on the app’s own cache.
  • Deactivate plugins you no longer use, and replace heavy ones that run on every page with lighter ones.
  • Schedule backup plugins and security scans for a quiet hour.

Block bad bots and xmlrpc.php attacks

Bots can send thousands of requests an hour. Block the ones you do not need. Never block Googlebot or Bingbot, or your pages can drop out of search.

  • In cPanel › File Manager, open public_html and turn on Show Hidden Files in Settings.
  • Download a copy of .htaccess before you change it.
  • If you do not use Jetpack or the WordPress mobile app, block xmlrpc.php. Add these lines at the top of .htaccess:
    <Files xmlrpc.php>
    Require all denied
    </Files>
  • To block a bot by name, add these lines above # BEGIN WordPress, with BadBot replaced by the name from the Visitors list:
    RewriteEngine On
    RewriteCond %{HTTP_USER_AGENT} BadBot [NC]
    RewriteRule .* - [F,L]
  • To block one IP address, open cPanel › IP Blocker and add it. If the site is behind a CDN, block it in the CDN instead.
  • Limit login attempts with a security plugin, to slow attacks on wp-login.php.
  • Load the site. If it breaks, upload the copy of .htaccess you saved.

Slow down cron jobs and clean the database

A cron job that runs every minute keeps the account busy all day. WordPress’s own scheduler, WP-Cron, also starts on page visits. A bloated database makes every page slower.

  • In cPanel, open Cron Jobs.
  • Change any job set to * * * * * (every minute) to */15 * * * * (every 15 minutes) or less often, if the task allows.
  • For WordPress, download a copy of wp-config.php first.
  • Add define( 'DISABLE_WP_CRON', true ); to wp-config.php, above the line that says “stop editing”.
  • Add a cron job that runs every 15 minutes, with your own domain in place of example.com: wget -q -O - https://example.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1
  • Download a backup of the database in cPanel › Backup before you clean it.
  • In LiteSpeed Cache › Database, clean post revisions, spam and trashed comments, and expired transients.
  • Or, in cPanel › phpMyAdmin, select the database, check all tables and choose Optimize table.

When the site has outgrown its plan

If the site still reaches its limits after caching and cleanup, it needs more resources than its plan gives.

  • Check Resource Usage, or ask support, whether usage stays near the limits on normal days.
  • Move to a bigger plan with more CPU and RAM.
  • For steady heavy traffic, or an app that needs its own server settings, move to a VPS. A VPS gives the site its own CPU and RAM, and you run the server yourself.

HostUpIndia Web & cPanel Hosting

HostUpIndia Web & cPanel Hosting runs on LiteSpeed with NVMe storage, so the LiteSpeed Cache plugin can cache your pages. Each plan card lists its CPU and RAM, and a bigger plan raises them. Every plan includes cPanel, free SSL, terminal (SSH) access, the AI Website Builder and daily backups kept 30 days.

  • From ₹49 a month on 3-year billing. Prices exclude 18% GST. See Web & cPanel plans.
  • Support tickets and email are received 24 hours a day, 7 days a week; WhatsApp is open for questions from 10 am to 7 pm IST, Monday to Saturday.
  • Free website migration by the HostUpIndia in-house team.
  • More help guides.