"You Are About to Reach the Connection Limit" and Other CloudLinux Resource Limit Errors

"You are about to reach the connection limit" is a CloudLinux warning on shared hosting. It means your account is close to its Entry Processes limit, which caps how many PHP requests your site can process at the same time. CloudLinux also caps CPU, memory, disk IO and file count. When a limit is reached, your site is slowed down or visitors briefly see a 503 or 508 error page. Your account is not suspended. The usual fix is to cut the work each page view causes: turn on caching, block abusive bots, control WordPress cron, clean the database and use a current PHP version. Move to a bigger plan only if real traffic still hits the limits after that.

This guide shows you how to read the Resource Usage page in cPanel, find the cause and apply the fixes in order. It applies to any CloudLinux-based cPanel account, including Cloudesta shared hosting.

Prerequisites

• A cPanel login for the affected hosting account.
• Administrator access to your site (WordPress admin if you use WordPress).
• A recent backup before you edit .htaccess or wp-config.php. JetBackup in cPanel works for this.
• Optional: cPanel Terminal access for WP-CLI commands, if your account has it.

What are CloudLinux LVE limits?

CloudLinux puts each cPanel account in its own Lightweight Virtual Environment (LVE). The LVE stops one busy site from slowing down everyone else on the server. The main limits are:

• CPU (SPEED): the share of CPU your account can use. At the limit, requests are slowed, not refused.
• Physical memory (PMEM): the total RAM used by all your processes. At the limit, new processes can fail, often with 500 or 503 errors.
• Entry Processes (EP): how many requests (mostly PHP) can run at the same moment. This is the "connection limit." At the limit, new visitors get a 503 or 508 error until a slot frees up.
• Number of processes (NPROC): all processes, including cron jobs and SSH sessions.
• IO and IOPS: disk throughput and disk operations per second. At the limit, imports, backups and uncached pages slow down.
• Inodes: the number of files and folders. These are counted under cPanel's File Usage statistic. At the limit, uploads, email delivery and cache writes fail.

1. How do I check resource usage in cPanel?

Log in to cPanel and go to Metrics → Resource Usage. The dashboard tells you whether your account was limited in the last 24 hours. Click Details to see the graphs.

• Usage line: how much of each resource your account used over time.
• Limit line: your plan's ceiling for that resource.
• Faults: how many times the limit was actually hit. Faults are the number that matters. High usage with zero faults is fine.

Change the time range to 7 or 30 days to spot patterns, such as faults at the same hour every day. If you see a Snapshot option, open it for a fault period. It lists the processes, URLs and MySQL queries that were running at that moment, which often points straight to the culprit. You can see inode usage under File Usage in the cPanel statistics sidebar.

2. What usually causes resource limit errors?

• Heavy WordPress plugins: page builders, related-post plugins, statistics plugins and security scanners that run on every request.
• wp-cron: it runs on page loads, so busy sites start it again and again.
• Bots and scrapers: aggressive SEO crawlers, AI scrapers, and brute-force attacks on wp-login.php and xmlrpc.php.
• Uncached pages: every visit runs PHP and MySQL from scratch.
• Outdated PHP: PHP 7.x is noticeably slower than PHP 8.x and uses more CPU per request.
• Too many simultaneous connections from one source: a misbehaving app, an uptime checker set to every few seconds, or a small DoS attack.

3. How do I fix it? Start with caching

Caching gives you the biggest improvement. Cloudesta shared hosting runs LiteSpeed, so a cached page is served without starting PHP at all. That frees Entry Processes and CPU immediately. In WordPress, go to Plugins → Add New, search for LiteSpeed Cache, then install and activate it. Open LiteSpeed Cache → Cache and make sure Enable Cache is ON.

Remove any other page-cache plugins, such as WP Super Cache or W3 Total Cache. Two cache plugins at once cause conflicts.

4. How do I block bad bots with .htaccess?

Open Files → File Manager and go to public_html. Enable Show Hidden Files in Settings, then edit .htaccess. Add these rules at the very top of the file:

# Block aggressive crawlers
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (AhrefsBot|SemrushBot|MJ12bot|DotBot|PetalBot|Bytespider|BLEXBot) [NC]
RewriteRule .* - [F,L]

# Block XML-RPC (often abused for brute force)
RewriteRule ^xmlrpc\.php$ - [F,L]

5. How do I stop wp-cron from overloading the site?

Edit wp-config.php in public_html. Add this line above /* That's all, stop editing! */:

define( 'DISABLE_WP_CRON', true );

Next, run cron on a fixed schedule instead. Go to Advanced → Cron Jobs, choose Once Per Fifteen Minutes as the common setting, and enter this command. Replace username with your cPanel username.

/usr/local/bin/php -q /home/username/public_html/wp-cron.php >/dev/null 2>&1

6. How do I optimise the database?

Slow queries hold PHP processes open longer, which uses up Entry Processes. You can clean the database in two ways:

• phpMyAdmin: go to Databases → phpMyAdmin and select your database. Click Check all, then choose Optimize table from the dropdown.
• WP-CLI: if Advanced → Terminal is available, run these commands:

cd ~/public_html
wp transient delete --expired
wp post delete $(wp post list --post_type=revision --format=ids) --force
wp db optimize

The second command prints an error if there are no revisions to delete. That is harmless. To stop revisions from piling up again, add define( 'WP_POST_REVISIONS', 5 ); to wp-config.php.

7. How do I update PHP?

Go to Software → Select PHP Version (the CloudLinux PHP Selector). Choose PHP 8.2 or 8.3 and click Set as current. On the Extensions tab, make sure opcache is ticked.

If your account uses MultiPHP Manager instead, set the version per domain there. Update your themes and plugins first. After switching, check your site for errors.

Verify it works

Check that pages are served from cache. Run this command on your own computer:

curl -sI https://example.com/ | grep -i x-litespeed-cache

Run it twice. The second run should show x-litespeed-cache: hit. Then wait 24 to 48 hours and reopen Metrics → Resource Usage. Fault counts for Entry Processes and CPU should be at or near zero.

Common problems

Visitors get "503 Service Unavailable" or "508 Resource Limit Is Reached"

This means the Entry Processes limit was hit. Use Snapshot to find slow URLs; long-running scripts and bot traffic are typical causes. Enable caching and block abusive user agents. Also check that no external service is polling your site every few seconds.

The site is slow only at certain hours

Compare the fault times with your scheduled tasks. Plugin backups, cron jobs, newsletter sends and crawler visits often run at fixed times. Move heavy jobs to off-peak hours and reduce how often they run.

Uploads or incoming emails fail even though disk space is free

You have probably hit the inode limit. Delete old backup archives, unused cache folders and stale sessions. Empty large email folders such as Spam and Trash.

500 errors with "Allowed memory size exhausted"

This is PHP's own memory_limit, not the LVE memory limit. You can raise it in Select PHP Version → Options. If physical memory faults also appear, find the plugin that uses too much memory instead of only raising limits.

When should I move to a bigger plan or a VPS?

Upgrade if you still see regular faults after all the steps above and your analytics show real visitor growth. Other signs are a WooCommerce or membership site with many logged-in users, which bypass the page cache.

To move to a larger shared plan, open a support ticket. Plan upgrades are handled by our team. For full control over resources, a Cloud VPS gives you dedicated CPU, RAM and root access.

Frequently asked questions

Will my account be suspended if I hit a resource limit?

No. CloudLinux slows down or temporarily refuses requests while you are at the limit, and everything returns to normal once usage drops.

Is the Entry Processes limit the same as the number of visitors?

No. It counts requests being processed at the same instant, and most finish in a fraction of a second. A well-cached site with a low EP limit can serve many thousands of visitors a day.

Can support tell me exactly what is using my resources?

Yes. Open a ticket with the time of the faults, and we can review server-side logs alongside your Resource Usage data.

Need help? Open a support ticket at https://cloudesta.com/submitticket.php and include your domain and the times the errors appeared.