Ошибка 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.

Are you seeing the 508 error upon visiting your website? Do you want to know what it is and how to get rid of it? You’re at the right place!

The error 508 resource limit is reached occurs when you have exhausted the resources (CPU, RAM, bandwidth, etc.).

This is a complete guide where we will see why error 508 occurs, how to fix error 508, and we will also see some of the ways to prevent this error.

Let’s begin with the error overview and understanding what it is.

When you see the 508 resource limit reached error, it simply means that your account is constantly exceeding the allocated resources. Typically, these resources include CPU usage, RAM utilization, or the number of concurrent processes running on your account.

You will see all these details on the side of your cPanel. If your account exceeds one or more of these resources, your website will start showing the 508 Resource Limit reached error.

Along with this, you might also see an additional text saying. “The website is temporarily unable to service your request as it exceeded the resource limit. Please try again later“.

As the text suggests, your server was unable to serve the request. Therefore, you will have to wait till the resource usage is reduced. Thereafter, your website will run again.

But wait, should you wait, and will it fix automatically? Let’s first understand what are some of the reasons for error 508, and then, we will see how you can fix it.

What are the main causes for this Error?

There are many reasons why your resources might exceed the allocated limits, and your website starts showing the 508 error. Here, we have mentioned a few of the most common reasons for the same.

The reasons are sorted from the most common reasons to the least common. So, in most cases, your problem will be from the first few.

High traffic Spikes

The most common reason why resources are exhausted is the overload of traffic. Your website might have received a huge amount of traffic (hits or visits). There are many reasons for the same.

For instance, your post might have gone viral on social media, or your website was featured in a big magazine. In that case, your website will show the error until the traffic decreases or is mitigated.

Your website will start to work again if you increase the resources allocated for the website/account.

The bandwidth limit could exhaust if you were already consuming a significant amount of bandwidth. Your traffic gradually increases. So, it’s important to have more resources for your account.

If you have only exhausted bandwidth, you will also see another similar error saying bandwidth is exceeded.

DDoS attacks or Hacked site

A DDoS attack sends an unusual amount of traffic to your website, causing your resource limit to exhaust. There could also be some other attack instead of DDoS. Either way, if your website was hacked, you can simply install Wordfence and run a scan.

You might have unknowingly installed some malicious files which are causing the issues. The Wordfence scan will fix all the issues. Thereafter, you can connect your website to Cloudflare CDN, providing an additional layer of security.

Poorly Written Code

If a page is taking more than usual time to load, there could be code issues. It increases the page requests as the user agent (browser) will keep requesting the page until it’s loaded.

If there are issues with the code, the page will take more time to load.

Once the request limit exhausts, your website will show the 508 Resource Limited is Reached error.

Backend Operations

Backend operations include cron jobs, import/export, backups, scanning, etc. There are also database operations, such as the execution of complex queries. These operations take a lot of your resources.

So, if you are exporting or importing a huge amount of data on your website, the resource limit might be exhausted. Once the operation is completed, the website will be back, or you can also consider terminating them.

WebCrawler Requests

Webcrawler requests issue is very rare. When the number of crawl requests per second increases, you will see a resource limit error.

Usually, the requests only increase if you have submitted your website to all the search engines and directories using a bulk submission tool.

Always make sure you have some kind of spam filter on. Spam in comment sections will also use your resource limit.

Also, if you have unfiltered contact forms, spammers use them to send massive spam submissions. So, always filter your spam to avoid this. You can use the Akismet plugin for this.

Third-party applications

If you are using WordPress or any other CMS, you should always use plugins from a reliable developer. A poorly coded plugin is like a timebomb, which can cause issues anytime.

For example, when WordPress releases a new version of a third-party app that is incompatible with it. It will start misbehaving (malfunction or it gets on a loop), causing issues to your website and resources.

Sometimes, even other pieces of software running on your server will be using the outdated plugin. So, make sure you check the compatibility before you update any software/plugin/code.

You can find the script or app that is “resource intensive” and disable it. We will talk more about it in the next section.

How to Fix 508 Resource Limit Reached Error?

Now that you know the possible causes of the issues, let’s see how to fix the 508 resource limit error.

One might argue that you can simply wait until the resources cool down. However, that’s not always the best solution. In the majority of cases, the error comes due to an ongoing issue.

For instance, if there is a spike in traffic, you can’t simply wait for it to solve. Instead, you need to take some steps to either decrease the page size or increase the bandwidth.

Therefore, you will have to take action to fix error 508 on WordPress or any other website.

Check Resource usage

To begin solving any issue, you need to analyze it first. So you can check the resource usage.

In cPanel, there is a direct option called “Resouce usage” in the metrics section. You can click on it and see the overview of the usage.

In the dashboard tab, it will show if the resource limit was reached or not. You can click on details to view the chart and the exact timing when the resource limit was reached.

In some panels, you can head to Analysis & Log Files >> Resource Usage Overview. You can also see if there are any warnings.

You will have a rough idea of which resource is exceeding.

Disable all Plugins and Activate Them One by One

Disabling all the plugins and reactivating them is the best way to solve any error, including Error 508 resource limit is reached.

It will quickly solve all the issues, and your website will work again. There are many ways you can disable all the plugins. The simplest way would be to go to the file manager and rename all the folders or the main folder.

Some CMS have many plugins installed to extend the functionality. Some of these outdated plugins might use intense resources. So, it’s better to deactivate them or find better alternatives.

Check Log Files

Log files play a very important role when you are debugging an issue. To view the error log, you can head over to the file manager and open the root of your website.

You will find a log file named “error_log”. Open the file and check recent entries to find the possible cause of the 508 error.

Keep everything updated

Most users are using a CMS system. In that case, you should always keep everything updated. Before you hit the update button and update everything simultaneously, you must check the compatibility.

Plugins and scripts from reliable providers are usually compatible with all the versions. However, this is not the case with the plugins from small developers teams or individual developers.

For instance, if you update WordPress core, popular plugins like Wordfence or MonsterInsights will have no issues. However, small plugins might misbehave. So, you should keep that in mind.

Database optimization

Database optimization is a crucial part of optimizing your website. If your website uses MySQL, you can optimize your database using phpMyAdmin.

NOTE: you should take the backup of your database before doing this as it might cause issues if not done right.

Select the database you want to optimize, select all the tables from the bottom of the page, and select optimize from the options.

Contact Support

If nothing works, you can contact your hosting support. They have more capabilities than you.

They can provide more information or even fix error 508 for you.

Preventative Measures

When your website goes down due to error 508, it leaves a bad impression among your users. So, here are some of the ways to prevent the error from happening in the future.

• Always monitor your resources. Keeping an on the resource usage will give you enough time to prevent the website from going down.
• Make sure your website has clean code and is error-free. Keeping plugins, themes, and core files updated is one of the ways to ensure a safe environment.
• Along with this, you should try to optimize the resources which are constantly exhausted. For instance, if you are running out of bandwidth, try optimizing images and page size.
• If you constantly run out of resources, you should try shifting from shared hosting to a VPS or a cloud server. In the same way, if you are using VPS, try going with a dedicated server.

Conclusion

Getting an error 508 resource limit reached is a common issue faced in shared hosting. It simply means that you have exhausted the resource limit.

To get your website working again, you can try freeing up the resources by disabling the plugins/site or upgrading your plan.

In shared hosting, the resources are not only limited but also shared. So, running out of resources is quite common.

If you tried everything mentioned above and still have no success, you can try upgrading your plan or shifting to a VPS. There are many affordable VPS that are priced as low as shared hosting.

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 ошибка на сайте может возникать при нехватки оперативной памяти. Для исключения данной проблемы необходимо посмотреть потребление оперативной памяти в панели управления хостинга.

Ошибка появляется также при исчерпании дискового пространства или лимита на число файлов и папок. В данном случае проверьте данные лимиты в панели управления хостингом, при необходимости удалите ненужные данные или перейдите на следующий тарифный план.

504 Gateway Timeout

Если 504 ошибка появляется при открытии сайта через продолжительное время, то это значит, что скрипт не выполнился за заданное ему время, по умолчанию это 60 секунд.

502 Bad Gateway

В случае, если 502 ошибка возникает моментально и на всех сайтах, обратитесь в технический отдел, обычно это означает проблемы в работе веб-сервера.

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.

Table of Contents