Resource limit reached (Error 508)

Shared Hosting · What HTTP 508 means on shared hosting and how to get the site working again.

What should I do when I get Resource Limit reached (Error 508)

Error 508 (Resource Limit Reached) means your shared hosting account hit a CloudLinux limit. The web server stopped that request so it cannot starve other customers on the same machine.

Typical limits include CPU, RAM, I/O, entry processes (concurrent PHP connections), and inodes (number of files).

What to do first

  1. Open DirectAdmin and check Resource usage / CloudLinux stats. See which bar is at 100%.
  2. Wait a minute and reload the site. Many limits reset quickly once the spike is over.
  3. If the site stays down, reduce load (steps below) or open a ticket.

Common causes

  • A plugin, theme, or cron job using too much CPU or memory
  • A traffic spike, bot crawl, or brute-force login attempts
  • Too many concurrent PHP requests (no cache, heavy admin-ajax, or a loop)
  • Hitting the inode limit (too many files — caches, backups, or uploads)
  • A compromised site sending spam or mining

How to fix it

  • Disable recently added plugins or themes and test again.
  • Enable a caching plugin (or the one you already have) so PHP does not run on every hit.
  • Limit login attempts and block abusive bots in .htaccess or a security plugin.
  • Delete leftover caches, old backups, and unused uploads if inodes are full.
  • Scan for malware if usage is high with little real traffic.
  • Avoid running miners, video converters, or other heavy jobs — those are not allowed on shared hosting.

If you need more CPU, RAM, or processes than the plan allows, upgrade or move the site to a VPS.

Error 508 is a resource error, not a DNS or SSL problem. Fixing nameservers or reissuing a certificate will not clear it.