508 Resource Limit Is Reached
The website is temporarily unable to service your request as it exceeded resource limit. Please try again later.
Ошибка означает исчерпание доступных ресурсов. Обычно это срабатывание лимита на число одновременных соединений, число максимальных процессов или лимит на оперативную память.
Для выяснения точных причин необходимо смотреть статистику потребления ресурсов в панели управления хостингом.
503 Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Чаще всего ошибка возникает из-за ошибок в файле .htaccess, если Вы очищаете этот файл, а ошибка не пропадает, проверьте права на файлы и папки. Они должны быть 644 на файлы и 755 на папки. Если с правами всё в порядке, возможно проблема в скрипте.
Для того, чтобы более точно определить причину возникновения ошибки необходимо смотреть лог ошибок сайта.
Также ошибка 503 на сайте может возникать при нехватки оперативной памяти при выполнении скрипта. Для исключения данной проблемы необходимо посмотреть потребление оперативной памяти в панели управления хостинга.
Ошибка появляется также при исчерпании дискового пространства или лимита на число файлов и папок. В данном случае проверьте данные лимиты в панели управления хостингом, при необходимости удалите ненужные данные или перейдите на следующий тарифный план.
502 Bad Gateway
Если ошибка 502 при открытии сайта появляется через продолжительное время, то это значит, что скрипт не выполнился за заданное ему время, по умолчанию это 60 секунд.
В случае, если ошибка возникает моментально и на всех страницах сайтах, обратитесь в технический отдел.
404 Not Found
The requested URL was not found on this server.
Ошибка 404 на сайте значит, что запрашиваемый файл или каталог не найден. Проверьте, верен ли адрес или проверьте наличие файла или каталога.
403 Forbidden
You don’t have permission to access on this server.
403 ошибка на сайте обычно означает отсутствие index.php или index.html файла. Иногда ошибка может возникать из-за нехватки прав доступа, проверьте их. Они должны быть 644 на файлы и 755 на папки. Если с правами всё в порядке, то возможно доступ запрещен в файле .htaccess.
Что делать, если на сайте отображается ошибка 508 (Resource Limit Is Reached)?
Автор: Arnas Damasickis
Обновлено более недели назад
Ошибка 508 (Resource Limit Is Reached) означает, что Ваш сайт превысил один (или несколько) из лимитов выделенных ресурсов. В большинстве случаев основной причиной является количество одновременно запущенных процессов (в том числе Entry Process). Чтобы узнать наверняка, откройте управление Вашим хостинг-аккаунтом, найдите Статистику использования заказа и проверьте графики.
Примечание: графики потребления ресурсов обновляются раз в 15-30 минут, потому если ошибка только-только появилась на сайте, может потребоваться подождать, чтобы увидеть актуальные значения.
Что делать сразу?
Если судя по графикам сайт превышает количество одновременно запущенных процессов, то Вы можете вернуть сайт онлайн уже через пару минут, просто остановив активные процессы. Для этого перейдите на страницу Хостинг → Управление → Сбросить аккаунт и нажмите Остановить запущенные процессы:
Что делать потом?
После этого начинается самое главное: оптимизация сайта. Тут действует очень просто правило: чем больше оптимизирован сайт, тем меньше ресурсов он тратит для работы и тем быстрее открывается. Звучит неплохо?
Есть множество сервисов, позволяющие проверить, насколько хорошо оптимизирован сайт, например GTMetrix, Google Page Speed и другие. Всё, что нужно для оптимизации, это проанализировать сайт с помощью одного из них, получить персонализированные рекомендации и выполнить их.
Обратите внимание, что иногда сайт может загружаться достаточно быстро, но при этом быть плохо оптимизирован:
Такие сайты тоже нужно оптимизировать.
Если Вы оптимизируете скрипты и потребление ресурсов, то 508 ошибка больше не будет возникать.
А если не помогло?
Если Вы проверили все варианты, максимально оптимизировали сайт, но он всё ещё потребляет почти все ресурсы, похоже, что Ваш сайт перерос текущий тарифный план. Это абсолютно нормально и закономерно происходит в процессе развития сайта. Всё, что Вам нужно сделать в таком случае, это изменить тариф на более высокий 😊
К слову, как только Вы перейдете на более высокий тарифный план, оставшиеся деньги из предыдущего плана будут пересчитаны и добавлены как дополнительные дни использования хостинга.
Coming across “Error 508. Resource Limit Is Reached” can put you off balance. It’s not a common HTTP error, but it can make both your site and webserver inaccessible.
But fret not. This article will explain what the HTTP Error 508 is, how you can troubleshoot it, and the preventative measures you can take to make sure that it doesn’t occur again.
Let’s get started!
Check out the video version
What Causes the “508 Resource Limit Is Reached” Error?
Most web host accounts have set limits on resources. If this limit is breached, a “508 Resource Limit Is Reached” error is triggered, and your site will be temporarily inaccessible.
This error is triggered at the server level and can be caused due to various factors, including excessive strain on server CPU and RAM resources. It’s also commonly associated with a high demand for concurrent processes, often seen if your site experiences an unusually high traffic volume.
A spike in website traffic could also be the result of an attempted DDoS attack. In this instance, your site will trigger a “508 Resource Limit Is Reached” error once the available resources have been exhausted during the attack. However, you might not have to do anything to fix the issue!
If you consider this surge in web traffic to be a one-off event, then you might choose to wait it out and see if the traffic subsides.
If you’re on a shared server, or you’ve subscribed to an entry-level hosting package, it’s more likely you’ll run into this type of error. If that’s the case, you’ll need to raise the resource limits in the short term to get your site back up and running again.
It might not be common, but when HTTP Error 508 does pop up, it can cause major problems for your site and your webserver. 👀 Learn how to fix it right here ⬇️Click to Tweet
How to Fix the “508 Resource Limit Is Reached” Error
When seeing higher traffic volumes than expected, your site can quickly exceed allocated resources, resulting in your server grinding to a halt.
Check Your Resource Usage
The first thing you can do to fix a resource limit error is to check your resource usage. Be sure to view server activity logs too. That’ll help in identifying the root cause of the problem.
If you’re a Kinsta customer, then you can view resource usage and activity logs quite easily.
Log into your MyKinsta dashboard and select the site you wish to view. You can view the resource usage via the Analytics menu and activity logs via the Activity Log menu.
There are additional tools and methods you can use to supplement this as well.
Bear in mind that the limits you see imposed on your site will be slightly less than the limits required to keep it running.
Why is this?
Let’s say your website is on a shared server, along with many other customers and their sites (bear in mind this wouldn’t be the case with Kinsta). As your site starts to attract more traffic, the server that hosts all these many websites, including yours, is processing more and more requests to accommodate your growing traffic.
If your popularity trend continues, the server will eventually hit its resource limits for every site it’s hosting, including yours. You can spot this trend early to prevent downtime. A good hosting provider keeps a watchful eye on the volume. Your web host should contact you to warn you that your site will go down if it continues to consume resources at a higher rate than your plan permits.
Check Internal Processes Running on Your Site and Third-Party Code
The cause of a “508 Resource Limit Is Reached” error may not always be external. Resources can be excessively consumed by one or more rogue processes running internally on your site, such as:
- Site backups
- Cron jobs
- Long or complex database queries
- A hacked site running a harmful script
- Third-party code
In the case of third-party code, this can often be down to a particular Content Management Solution (CMS) extension. If, for instance, you’re running WordPress and have one or more plugins installed that are regularly consuming more resources than are allocated, then you’ll run into 508 errors sooner or later.
To avoid such a situation, it’s advisable to keep your CMS extensions up to date. With WordPress, this means keeping your themes and plugins updated to the latest versions.
If no update has been available for a particular theme or plugin for a while, then consider discontinuing using it in favor of a similar, more recently updated product or contacting the author to check if a new version is imminent.
Deactivate All Your Site’s Extensions and Enable Them One by One
It could be that one of your CMS extensions is consuming more server resources than it should—in which case you should try disabling them all. If the error vanishes, then your suspicion is confirmed—an extension is a culprit.
Begin by deactivating the site’s extensions.
Once all extensions are deactivated, reactivate them one at a time, retesting your site each time to identify the culprit. Your next course of action should be to contact the extension author to report the issue. If the extension is well maintained, its author should get back to you with a workable solution.
Deactivate Your Child Theme
Finally, if you’re using a WordPress child theme, you should check the changes that have been made to it to see if they could be causing any issues. You can quickly test this by temporarily swapping to the parent theme.
Contact Support
If none of those above ways helped you pinpoint the cause of the increased resource usage, you should contact your web host’s support team and ask them for more detailed information. Kinsta’s support team is available 24/7.
Preventative Measures
It’s a good idea to keep one eye on server resource usage as a preventative measure. It will give you a chance to get ahead of any potential issues that could bring your site down.
Self-maintenance is a sensible approach to helping keep hosting costs under control as your site grows and matures while simultaneously making sure your site’s downtime is minimized. Ideally, you’ll want to stay well below the allocated resource limit to reduce the risk.
Many add-on applications can help you keep track of your site’s usage. An application performance monitoring tool (like Kinsta APM) should be a top consideration when deciding how to keep watch over your site.
If you’re running any promotions or marketing drives, then expect and prepare for increases in site traffic. It can help to understand how your hosting provider counts visits to your site. In most cases, you won’t necessarily see a massive spike in traffic, but it’s still sensible to try and predict whether you’re likely to run close to your limits.
Additionally, make sure that your contact details (phone and email) are always up to date. That way, you won’t miss any resource usage alerts.
For peace of mind, we recommend investing in a dedicated webserver, or—barring that—a higher allocation of initial resources, such as with Kinsta’s disk space add-on. Having this flexibility will cost more, but the chances of your website going down will drop to nearly nothing.
Don’t let an HTTP Error 508 message ruin your day. 😥 With these quick tips you can troubleshoot it and take preventative measures to stop it from happening again👇Click to Tweet
Summary
When your site hits a “508 Resource Limit Is Reached” error, it can be challenging. You’ll want to get things back up and running as soon as possible. To prevent this error from happening again in the future, you should:
- Fix the current issue by checking what’s causing the high resource usage and
- Raise your site’s resources limits to take into account future growth and traffic as well
For more, check out how Kinsta does things differently with Google Cloud infrastructure and isolated software containers for each site.
Error 508 occurs when you exceed the resource limits in your plan. There are several reasons that can cause this.
In this guide, 508 error: how to solve it, we will see what are the possible causes of the error 508. Based on the origin of the problem, we’ll also see how to solve it, in order to get the site accessible again and avoid the error from recurring.
To start with, let’s see what is meant by resource limits and what systems are used to keep consumption under control.
Error 508 and resource limits
Hosting resource limits are used to ensure that all sites hosted on the server are functioning properly, without overloads that compromise one or more sites.
The moment these limits are exceeded when trying to visit the site you will see an error page with a warning like this:
Error 508 Resource Limit Is Reached
How is resource management monitored?
Our servers are equipped with CloudLinux, a management system designed specifically for hosting environments.
CloudLinux uses a technology called LVE or Lightweight Virtual Environment. This system allows you to isolate individual accounts and limit resources. Thus, by imposing limits on the use of CPU, RAM, I/O and the number of processes, you can get a proper distribution of resources.
The goal is to prevent a single user from overloading the entire server, causing problems for all users sharing the same server. A situation that could occur in a shared hosting, but that can be avoided by adopting this system.
In the absence of such systems, and before they were adopted, the sudden spike in traffic of a single site was able to cause disruption to all sites hosted on the same machine. In such a situation, you would have had the site down because of an excessive request of resources from another site hosted on the same server.
What happens when you exceed your resource limit?
First, we need to understand what kind of resources we are talking about. CloudLinux monitors the usage of RAM, CPU, I/O and the number of processes.
Error 508 or, as we will see other errors 5xx, occur when an account exceeds the threshold of allowed resources. For example, exceeding the memory usage or the maximum number of processes allowed.
Let’s see what happens in the different cases.
If you reach the set memory limit, the system will first try to free memory, starting with the cache. If the memory is still insufficient, some processes will be terminated.
This will result in error 500 or error 503. These are temporary errors that are removed automatically as soon as you are within the limits.
When the CPU limit is reached, the system first slows down the running processes to keep them within the limits. If, on the other hand, the maximum number of processes is exceeded, you get error 508.
When the I/O limits are exceeded, i.e. reading and writing data on the disk, CloudLinux slows down the processes in progress so as to keep them within the limits, in these cases the site remains active.
How to check the resources used by your site
You can check your resource usage and see if you’ve exceeded your limits by checking your account metrics from your control panel.
Log in to cPanel and open the “Resource Usage” tool from the metrics section.
This will allow you to see if your site has been forced back into the limits recently. For real-time consumption just click on Current usage as you see in this screenshot.
Error 508: possible causes and how to solve it
We have seen that error 508 appears when you exceed your account limits, but what is behind it, how can you solve it?
Identifying the causes of error 508 is the only way to solve the problem. Let’s take a look at the possible causes and what methods we can use to fix them.
High traffic and DDoS attacks
Among the most common situations that can lead to an error 508, is a spike in traffic.
You might have a sudden increase in traffic to your site after starting an advertising campaign. In this case, since this is a situation that you can predict, you should take action beforehand, perhaps switching to a plan with more resources.
The traffic spike, however, can also be unexpected. In that case, you can assess whether it is an isolated event and wait for the traffic to return to normal.
In other circumstances, however, an unusual increase in traffic could be due to a DDoS attack that tries to overwhelm the server with continuous requests.
To prevent such attacks, CloudLinux monitors the number of simultaneous connections (entry process) that occur on the site. If the limit is exceeded, error 508 appears.
Spam in the comments section
Contact forms are often targeted by bots with the goal of automatically sending massive amounts of spam comments.
While the bot is in action, multiple connections are opened, exhausting the available resources. As a result, the limits are exceeded and error 508 is displayed to anyone trying to visit the site.
One of the methods to avoid spam in comments is to use the CAPTCHA code.
Executing processes
There are several processes that can be resource-intensive and cause the error 508. Some common situations are an ongoing site backup process, or while running a cron job.
Similarly, a particularly complex database request can also be responsible for error 508.
If your site has experienced a hacker attack, the massive resource usage could be coming from a malicious script that is running without your knowledge. In this case, the first thing to do is to analyze the access logs to the site.
The entry process limit can also be exceeded if your site is undergoing a brute force attack. This type of attack involves trying to access a site using combinations of username and password to try to find the correct ones.
At SupporHost we use proprietary rules to protect your site from this type of attack. In any case, remember that using long and complex passwords is crucial to keeping your site safe.
Third-party applications
In detail, you should also pay attention to third-party applications and scripts used. An example may be a WordPress plugin or theme that requires more resources than it should.
The best way to avoid such problems is to keep WordPress plugins and themes up to date and avoid using applications that are not updated frequently.
If you want to make sure that the error 508 is caused by a massive resource usage of a plugin you can do a test. First, deactivate all plugins (this applies to themes as well) and check if the error still occurs.
If the error does not appear anymore, you will have to figure out which plugin is causing the problem. To do that, reactivate the plugins one by one and check continuously if error the 508 reappears after you’ve reactivated each plugin.
In case you manage to identify the “culprit” there are three alternatives. First, check if there are any available updates, update the plugin and try to see if the error has been fixed.
If there are no updates available, try to contact the developer. Reporting the error will ensure that other users do not end up in the same situation as you.
In case you can’t solve it, you will have to find an alternative to the plugin (or an extension) you were using.
If you have a WordPress site you can find a plugin that has the same functions by searching in the official directory. For Joomla you can check the extensions directory and for PrestaShop the modules directory.
It’s clear that you certainly care about the performance of your site and you know how important it is to have a fast site, so remember to avoid plugins that slow down WordPress.
Upgrade the plan: when is it necessary?
As we have seen, the first thing you should do is to rule out the possibility that the cause is a resolvable problem.
Among the cases we’ve looked at is an attempted hacker attack, a site targeted by spam, or a plugin that takes too many resources.
You also have to consider possible problems with the code due to adding site features that use resources disproportionately. Exclude the possibility that it is a temporary problem, such as a backend operation: from running a backup to a database query.
If you’ve ruled out all possible causes, it means your site really needs more resources. The most likely scenario is that you’re registering more visitors. If this trend becomes the norm, it means that it’s time to switch to a plan with increased resources.
In case your plan is a shared hosting you can consider switching to a semi-dedicated hosting. Or if the resources of the latter are not enough, you can choose a dedicated solution: a VPS cloud hosting or a dedicated server.
With SupportHost, you can upgrade at any time, without any disruption and only pay the difference.
Conclusion
In this article, 508 error: how to solve it, We’ve seen the possible causes of the error 508, an alert of this type tells you that your site is using more resources than your plan provides. Among the causes we’ve examined there can be a programming error, a plugin that doesn’t work properly or an unauthorized access attempt.
In all these cases by taking action at the source of the problem, the error can be fixed. When the 508 error is caused by the consumption of resources that actually serve your site and it’s not just a temporary traffic spike, all you need to do to resolve it is to switch to a higher level.
Have you ever encountered error 508 on your site? Were you able to identify the cause and fix it? Let me know in the comments below.
Как исправить ошибку 508. В общем, это довольно легко исправить. Как всегда, если вы являетесь пользователем, который получает эту ошибку, мы настоятельно рекомендуем перезагрузить страницу с помощью CTRL / CMD — Shift — R, чтобы обойти кеш, а затем очистить кеш вашего браузера, чтобы убедиться, что что-то не зависает на вашем конец.
В этой спецификации клиент может послать запрос,содержащий декларацию расширения,которая описывает расширение,которое будет использоваться.Если сервер получает такой запрос,но все описанные расширения не поддерживаются для данного запроса,то сервер отвечает кодом состояния 510.
Код состояния ответа 508 Loop Detected протокола передачи гипертекста (HTTP) может быть задан в контексте протокола Web Distributed Authoring and Versioning (WebDAV). Это указывает на то, что сервер завершил операцию, потому что он столкнулся с бесконечным циклом при обработке запроса с «Глубина: бесконечность».