Era Host hosting
EraHost – Free Domain, Cheap Hosting!
Client Area
Support 24/7
Menu

Error 508: Resource Limit Reached

3 min read
13.06.2025

What is Error 508?

The 508 Resource Limit Reached error occurs when a hosting account exceeds the allocated server resources, such as CPU, RAM, or entry processes. This error is common on shared hosting plans where server resources are limited to prevent one user from affecting others on the same server.

Error 508 Resource Limit Reached
HTTP 508 — CloudLinux says "this account is at the cap."

For closely related CloudLinux / shared-hosting topics, see CloudLinux Hosting — Why Is It Secure? and Understanding the .cagefs Folder in CloudLinux.

Causes of Error 508

  1. Exceeding Entry Process Limits:
    • Entry processes refer to the number of concurrent connections to your website (e.g., active PHP scripts, visitors).
  2. High CPU or RAM Usage:
    • A poorly optimized website or a sudden traffic spike can consume excessive CPU or memory.
  3. Too Many Executions:
    • Running too many scripts or plugins simultaneously can trigger the limit.
  4. Excessive Cron Jobs:
    • Misconfigured or frequent cron jobs can consume resources unnecessarily.
  5. Malicious Activity:
    • Bot traffic, DDoS attacks, or malware on your site can quickly exhaust resources.
Linux Hosting
Reliable and fast web hosting!
  • Free domain
  • Modern servers
  • NVMe disks
  • 7-day free trial
Linux Hosting

How to Fix Error 508

Check Resource Usage

  • If Using cPanel:
    1. Log in to cPanel.
    2. Go to Metrics > Resource Usage.
    3. Review recent resource usage and identify spikes.
  • If Not Using cPanel:
    • Contact your hosting provider for detailed usage logs.

Optimize Your Website

  • Reduce Plugins and Scripts:
    • Disable unnecessary plugins, especially resource-heavy ones.
    • Minify CSS, JavaScript, and HTML files.
  • Enable Caching:
    • Use caching plugins like WP Super Cache or W3 Total Cache for WordPress.
    • For non-WordPress sites, enable caching in your server configuration.
  • Optimize Database:
    • Use tools like phpMyAdmin to optimize database tables.
    • For WordPress, use plugins like WP-Optimize.
  • Compress Images:
    • Use tools like TinyPNG or plugins like Smush to reduce image sizes.

Upgrade Hosting Plan

  • If resource usage is consistently high, consider upgrading to:
    • A higher-tier shared hosting plan.
    • VPS hosting for dedicated resources.
    • Cloud hosting for scalable resources.

Limit Entry Processes

  • Reduce Concurrent Connections:
    • Add this to .htaccess to limit connections:
    <IfModule mod_limitipconn.c>
        MaxConnPerIP 10
    </IfModule>
  • Use a CDN:
    • A Content Delivery Network (e.g., Cloudflare) reduces server load by caching static resources.

Manage Cron Jobs

  • Check cron job configurations in cPanel or manually through the terminal.
  • Limit the frequency of jobs that aren't time-sensitive.

Scan for Malware

  • Use security plugins or tools like Sucuri or Wordfence to scan your site for malicious activity.
  • Clean up infected files and apply security updates.

Reduce Bot Traffic

  • Block unnecessary bots using .htaccess:
    RewriteEngine On
    RewriteCond %{HTTP_USER_AGENT} bad-bot [NC]
    RewriteRule .* - [F,L]
  • Use tools like Cloudflare to filter malicious traffic.

Best Practices to Prevent Error 508

  1. Monitor Resource Usage Regularly:
    • Use tools provided by your host or third-party monitoring tools.
  2. Optimize Website Performance:
    • Regularly audit your website for speed and performance.
  3. Implement Security Measures:
    • Protect your site from bot traffic and DDoS attacks.
  4. Use Scalable Hosting Solutions:
    • For growing websites, consider hosting solutions like cloud hosting or VPS.
Frequently asked questions
In cPanel: "Resource Usage" → shows current vs limit for CPU, memory, I/O, entry processes. If you see a consistent peak at the limit, that's your bottleneck. As the host admin: `lveinfo --user= --period=1d` from root. The output shows fault counts per resource — highest fault count is the limit you're constantly hitting.
Number of simultaneous HTTP requests in flight for that account. Default limit 20 on most CloudLinux configs. A WordPress site getting a traffic spike or running a slow page (3-5 sec each) easily hits 20 in flight; the 21st request returns 508. Fix: cache (Cloudflare or WP cache plugin), speed up the slow pages, or upgrade the plan for a higher EP cap.
Check the slow request log: cPanel "Errors" tab plus webserver access log for unusually long response times. Common culprits: image-optimization plugins doing CPU work synchronously, security plugins scanning files on every request, SEO plugins hitting external APIs. Disable plugins one at a time and watch resource usage drop.
Limit raise needs `lvectl set ` AND a process restart for new limits to apply. Sometimes provider raises the package limit but doesn't re-apply to existing accounts. Ask them to confirm with `lveinfo --user=` showing the new limits. If shown correctly and 508 persists, the bottleneck is something else — back to identifying the actual resource hit.
Related articles
CloudLinux Test Page: What Can You Learn and What to Pay Attention To?
Fixing "A Fatal Error or Timeout Occurred While Processing This Directive"
MySQL Error #1227: Access Denied — You Need (at Least One of) the SUPER Privilege(s)