How to View Your Direct Admin Hosting Account Resources Usage & Limitation
Why You're Seeing 508 Resource Limit Is Reached?
If you're on a shared server and you're seeing this error message "508 Resource Limit is Reached", that indicates your account has exceeded one of the following components: CPU usage, RAM usage and/or the number of concurrent processes running under your Direct Admin account.
Login to your Direct Admin console and click on your target domain name.
Under Advanced Features, click on Resource Usage.
Then you will be able to view the resources usage graph for CPU usage, Memory usage and Concurrent connections.
NOTES:
Most of the time, a lot of resource usage issues are caused by badly coded scripts, such as 3rd party themes or plugins that are installed on CRMs such as Joomla, Magento and Wordpress blog etc.
SOLUTIONS:
If you own a Wordpress blog on your account that is causing the resource usage issues, we recommend disabling all plugins, and then monitoring the resource usage with those plugins disabled, you can then reactivate the plugins 1 by 1 until your find which is causing your issue.
If you're on a shared server and you're seeing this error message "508 Resource Limit is Reached", that indicates your account has exceeded one of the following components: CPU usage, RAM usage and/or the number of concurrent processes running under your Direct Admin account.
Login to your Direct Admin console and click on your target domain name.
Under Advanced Features, click on Resource Usage.
Then you will be able to view the resources usage graph for CPU usage, Memory usage and Concurrent connections.
NOTES:
Most of the time, a lot of resource usage issues are caused by badly coded scripts, such as 3rd party themes or plugins that are installed on CRMs such as Joomla, Magento and Wordpress blog etc.
SOLUTIONS:
If you own a Wordpress blog on your account that is causing the resource usage issues, we recommend disabling all plugins, and then monitoring the resource usage with those plugins disabled, you can then reactivate the plugins 1 by 1 until your find which is causing your issue.
Updated on: 12/11/2018
Thank you!