A 503 error is a server-side response code that indicates the server is temporarily unable to handle the request. This can occur for a variety of reasons, but in the context of a web hosting environment, it often suggests that the account is hitting its LVE (Lightweight Virtual Environment) limits, also known as "Resource Limits Reached".
What are LVE Limits?
LVE limits are designed to provide stability on the server by restricting each individual cPanel account to a set of resource limits, similar to how a Virtual Private Server (VPS) works. Each individual account typically has 1 CPU, 1GB RAM, and 30 Entry Processes, unless otherwise stated on your package. Only if the account hits its LVE limits would it display a 503 error, which is referred to as a 'fault'.
How to Resolve a 503 Error
The LVE limits are fairly high for a shared account, but they can be scaled if required by upgrading an account to the Elastic Cloud service. However, before considering an upgrade, it's recommended to review the plugins the site uses and check for any abnormal traffic. Here are a few things to check:
Review Your Plugins
Disable any unnecessary plugins. Ideally, temporarily disable them all, wait a couple of minutes, then re-enable them to see if that resolves the issue.
Try to enable caching on the site. We highly recommend Bolt-Cache, which was developed in-house and is available from cPanel -> Bolt-Cache. This can significantly reduce resource usage.
Check Your Cron Jobs
Cron Jobs that run heavy processes too frequently can cause an account to max out its LVE limits.
Review Backup Processes
Backup plugins or scripts can cause an account to max out its LVE limits due to the disk/memory-intensive processes required to generate the backups.
Monitor MySQL Processes
Processes that consume large MySQL throughput can also cause issues.
Check for Attacks
It's also possible the account is under some kind of attack.
You can check your LVE usage via the cPanel -> CPU and concurrent connections screen in cPanel. By analyzing the Snapshots as described in the document, you will be able to see the processes running at the time of hitting your limit.
Considering an Upgrade
If you've followed all the steps above and your account is still hitting its resource limits, it may be that your site is simply outgrowing its current hosting plan. This is especially likely if the resource limits are being reached due to genuine traffic and usage, rather than due to issues like unnecessary plugins or attacks.
At Brixly, we offer a wide range of hosting plans designed to cater to all kinds of requirements. If your site is growing and needs more resources to deliver a smooth and fast experience to its users, it might be time to consider an upgrade.
Our sales team is always ready to discuss your needs and help you choose the best plan for your site. Whether you need more CPU power, RAM, or Entry Processes, we can provide a plan that offers the resources you need.
Remember, upgrading your hosting plan is a normal part of the website growth process. As your site attracts more visitors and offers more features, it will naturally require more resources. Upgrading your plan is a positive step that shows your site is successful and growing.
So, if you're consistently hitting your resource limits and believe it's time for an upgrade, don't hesitate to reach out to our sales team. We're here to help you make the right decision for your site's future.
Need More Help?
If the above steps don't resolve the issue, we at Brixly would be more than happy to investigate this further for you. If you've spent some time reviewing the above and still can't resolve the issue, please don't hesitate to get in touch.