Skip to main content
Submit a request

"Resource limit reached" and 508 errors explained

Maxim Tsitsejev
Updated

Applies to: All plans

A 508 "Resource Limit Reached" error means your hosting account hit one of its resource limits for a moment, so the server briefly paused or refused new requests. It is not a full outage and your site is not hacked or deleted. The error clears on its own as soon as your usage drops back under the limit. Below is why it happens and what to do about it.

What a 508 actually means

Every account on our platform runs inside its own isolated container with set limits on CPU, memory and processes (this is CloudLinux LVE). Those limits keep one busy site from slowing everyone else down. When your site tries to use more than your plan allows — usually a traffic spike, a heavy plugin, or a slow database query — the server queues or briefly rejects extra requests. Visitors then see a 508 page until usage settles.

Think of it like a busy checkout: the shop is open, but for a few seconds there is a queue.

Common causes (most likely first)

  • A traffic spike — more visitors arrived at once than your plan's CPU or process limits can serve.
  • No caching — every visit rebuilds the page from scratch, multiplying the work.
  • Too many or heavy plugins — bloated WordPress plugins burn CPU and memory on every request.
  • Slow or runaway database queries — an inefficient query pins your CPU/IO.
  • A bot, scraper or brute-force attempt hammering the site.
  • Genuinely outgrowing your plan — sustained real traffic that needs more headroom.

Quick fixes

  1. Check your usage first. In cPanel, open the resource-usage / CloudLinux statistics tool to see which limit you are hitting (CPU/SPEED, physical memory, entry processes or IO). This tells you what to fix. See How to read your resource-usage stats in cPanel.
  2. Turn on caching. We run LiteSpeed, so for WordPress install and enable the LiteSpeed Cache (LSCache) plugin — it pairs with our server-level cache and is the single biggest win. See How to speed up WordPress with LiteSpeed Cache.
  3. Trim plugins and themes. Deactivate and delete anything you do not need. Replace heavy "all-in-one" plugins with lighter alternatives.
  4. Use a modern PHP version. Set PHP 8.x for your domain in cPanel -> Software -> MultiPHP Manager — newer PHP is usually faster and lighter. See How to choose the right PHP version for performance.
  5. Fix slow database queries. Optimise or remove queries and plugins that scan large tables. Our MySQL Governor smooths heavy database accounts, but a badly behaved query can still trip the limit.
  6. Block bad bots. If a scraper or login-attack is the cause, use cPanel -> Security -> IP Blocker to block the offending addresses.

Result: Once usage drops below your limits, the 508 stops appearing immediately — there is nothing to restart.

If that did not work

If your usage report shows you are consistently at your CPU, memory or process ceiling from normal, genuine traffic, you have simply outgrown your plan. The fix is to upgrade to a plan with higher limits — you can do this any time from client area -> Services -> My Services. See When should I upgrade my plan? and How to upgrade or downgrade your plan.

If the 508 keeps appearing and the cause is not obvious, start a chat with us and include the details below. On Managed plans, our team will help investigate; on Self-Managed plans we will point you to the likely cause, but optimising your application is your responsibility.

Related articles

Comments

0 comments

Please sign in to leave a comment.