Your visitors see “508 Resource Limit Is Reached” every day around 10 am, then it goes away. The server isn’t down, and your neighbours on the same server aren’t complaining: your account alone has hit one of its limits. That idea explains most of what happens on shared cPanel hosting: every account runs inside fixed limits enforced by CloudLinux, and every tool in the panel works within them. This guide covers where to manage everything in cPanel, how to read your account’s limits, how to use the terminal and uapi, and what lies behind the common errors.
01The cPanel map: what you manage where
cPanel’s current interface (Jupiter) groups its tools into sections, and you can search for any tool by pressing the / key. These are the everyday tasks and where to find them:
| Task | Tool | Practical note |
|---|---|---|
| Add a domain or subdomain | Domains | Keep each domain’s directory outside public_html so every site stays separate |
| DNS records | Zone Editor | Only takes effect if the domain uses the hosting’s name servers |
| Email Accounts and filters | Check SPF and DKIM in the Email Deliverability tool | |
| Files | File Manager and FTP Accounts | Use SFTP instead of unencrypted FTP |
| Databases | MySQL Databases, PostgreSQL Databases and phpMyAdmin | One user per application, with rights on its own database only |
| Certificates | SSL/TLS Status | AutoSSL issues and renews a certificate for every domain pointing to the server |
| Scheduled tasks | Cron Jobs | Send the job’s output to a file or silence it, or you’ll get an email on every run |
| PHP version | Select PHP Version | Version, extensions and values such as memory_limit in one place |
| Resources | Resource Usage | The first page to open when the site slows down |
02CloudLinux limits: how to read Resource Usage
CloudLinux puts every account inside an that caps what it can use of the server’s resources. An account that hits its limit gets slowed down or has new requests refused, while the other accounts stay healthy. Six limits matter to you:
| Limit | What it measures | What happens when you hit it |
|---|---|---|
| SPEED (CPU) | A share of one core: 100% means a full core | The account is slowed down, with no error message |
| PMEM (memory) | Physical memory of all the account’s processes | PHP processes are stopped and a 503 or 500 error appears |
| EP | Concurrent dynamic requests | A 508 error for new requests |
| NPROC | All processes: PHP, cron jobs and SSH | A 508 or 500 error, and cron jobs fail |
| IO | Disk read and write throughput | Heavy operations such as backups and unpacking slow down |
| IOPS | Disk operations per second | Slowness with many small files |
The (EP) limit is the most misunderstood. It isn’t the number of visitors; it’s the number of requests your account is handling at the same moment. A simple law governs it: concurrency equals request rate multiplied by request duration. A site receiving 5 dynamic requests a second, each taking 400 ms, keeps two processes busy on average. If the database slows down and each request now takes 4 seconds, the same traffic needs 20 processes, and the 508 error appears. So EP faults are usually a symptom of slow requests, not of too many visitors.
Here’s how to read the Resource Usage page: at the top, a notice if your account hit any limit in the last 24 hours; below it, a chart for each resource with the limit drawn as a horizontal line; then a table with the number of times each limit was hit (faults). Pick the period when the error appeared, find the limit whose faults rose in those same minutes, then match it against the access log (Raw Access) to see which pages or which addresses were requesting at that moment.
03Illevante’s cPanel plans in numbers
These are the three plans’ resources as Illevante publishes them; the CPU and memory figures correspond to the CPU and memory limits on the Resource Usage page:
| Resource | cPanel Start | cPanel Power | cPanel Infinity |
|---|---|---|---|
| CPU | 1 core | 2 cores | 4 cores |
| Memory (DDR5 ECC) | 1 GB | 2 GB | 3 GB |
| NVMe storage | 20 GB | 30 GB | 40 GB |
| Inodes | 250,000 | 375,000 | 600,000 |
| Domains | 5 | Unlimited | Unlimited |
| Mailbox size | 2 GB | Unlimited | Unlimited |
| Backup retention | 15 days | 30 days | 45 days |
| Estimated monthly visits | About 35,000 | About 75,000 | About 150,000 |
All three plans include LiteSpeed with LSCache, CloudLinux, Imunify360, JetBackup, Redis, PHP 5.6 to 8.5, MariaDB and PostgreSQL with unlimited databases, SSH and SFTP, Git, cron jobs, Node.js and Python, and AutoSSL certificates. The visit counts are estimates: what really sets your plan’s capacity is how long each request takes and how much is served from the cache.
The number that surprises site owners most is : every file, directory and email message uses one. A single node_modules directory can hold tens of thousands of files, a mailbox that hasn’t been emptied in years can too, and the cache files of a badly configured plugin can fill whatever is left. Watch the count in the statistics on the panel’s home page.
04Softaculous, PHP and backups
installs more than 280 applications, including WordPress, Joomla and PrestaShop, and creates the database and its user itself. Turn on automatic updates with a backup before each update; that covers the most common ways things break. We cover tuning WordPress for performance in a separate article on this blog.
In Select PHP Version you pick the account’s PHP version, enable the extensions your application needs such as intl, imagick and redis, and set values such as memory_limit and upload_max_filesize. Remember that memory_limit is a limit per process, while PMEM is a limit for the whole account: three processes allowed 512 MB each exceed the memory of a 1 GB plan.
JetBackup takes a daily automatic backup stored on separate servers, from which you can restore the whole account, the files, a specific database, the email, or a single file. Retention depends on the plan, so if you need a longer history, such as a monthly copy kept for a year, download a full backup every month and store it somewhere else.
05The terminal and uapi
The plans let you log in over SSH, or from the Terminal tool inside cPanel. That’s where uapi, cPanel’s programming interface on the command line, becomes the fastest route for repetitive tasks. It runs with your account’s permissions and returns results as YAML or JSON:
# Quotas and usage: disk and inodesuapi Quota get_quota_info# Domains attached to the accountuapi DomainInfo list_domains# Existing MySQL databasesuapi Mysql list_databases# A new database and a user with specific rights (both names start with your account name)uapi Mysql create_database name=nawras_shopuapi Mysql create_user name=nawras_app password='Replace-With-A-Long-Random-Password'uapi Mysql set_privileges_on_database user=nawras_app database=nawras_shop privileges=SELECT,INSERT,UPDATE,DELETE,CREATE,ALTER,INDEX# Installed certificates as readable JSONuapi --output=jsonpretty SSL list_certs
can be added from the Cron Jobs screen or with the crontab command. Here’s an example for a Laravel app’s scheduler every minute, with output silenced so you don’t get an email on every run; those emails use up inodes too:
# Replace /usr/local/bin/php with the path that which php returns(crontab -l 2>/dev/null; echo "* * * * * cd $HOME/apps/tawsil && /usr/local/bin/php artisan schedule:run >/dev/null 2>&1") | crontab -# Review the current jobscrontab -l
06Common errors and what lies behind them
Most errors visitors see on shared hosting come down to a limit the account hit or a wrong setting. These are the most frequent:
- Problem508 Resource Limit Is Reached at specific times
- FixOpen Resource Usage for that period: if EP or NPROC faults rose, look in the access log for slow requests or a bot flooding the site. Enable caching and block the source before you upgrade the plan.
- ProblemA 503 error or blank pages during a large import or export
- FixThe account hit its PMEM memory limit and PHP processes were stopped. Split the job into smaller batches, run it at a quiet time, and review memory_limit.
- ProblemEmail bounces with a “full” error although there’s free disk space
- FixMost likely you’ve hit the inode limit or the mailbox quota. Empty Trash and Spam, and delete old cache files and forgotten backups in the account’s home directory.
- ProblemAutoSSL won’t issue a certificate for a domain or subdomain
- FixValidation fails if the A or AAAA record points to another server, or if a CAA record doesn’t allow the issuer. Fix the records, check their propagation with Illevante’s DNS propagation check, then run AutoSSL from SSL/TLS Status.
- ProblemA 500 error after editing .htaccess
- FixA syntax error in the file, or a directive the server doesn’t support. Undo the last edit, and read the reason in the Errors tool under Metrics.
07Practical recommendation
Give yourself a ten-minute weekly routine: open Resource Usage and look for faults, check the inode count, make sure the last JetBackup backup completed, and update your applications. Keep PHP on a version that still gets security support, and turn anything repetitive into a script or a cron job instead of clicks you try to remember.
And if CPU or EP faults stay high on the Infinity plan even though your requests are fast and your cache works, it’s time for resources you don’t share with anyone. A CoreVPS server with a cPanel licence gives you those resources and keeps you on the panel you already know.
