Scan aborted: Too many server errors.

Hi @pstidsen,

The mentioned error meant that BLC was picking a lot of server errors and to prevent any overload the scan was aborted.

https://wpmudev.com/docs/wpmu-dev-plugins/broken-link-checker/#error-19-too-many-errors

I could also notice there a lot of URLs picked from a subdomain URL which starts with “no.domain.dk”, the “domain” would be the site URL.

How is the website supposed to work? Is that a separate individual site or a staging site?

To start with, could you please check and see what the current server resources are? And make sure memory_limit is 512M and max_execution_time is 300 and see if that helps with running a new scan successfully.

You can find that info via WP Dashboard under Tools > Site Health?in your WordPress dashboard and click on the?Info?tab. Expand??Server tab look for the PHP memory limit for memory_limit and PHP time limit for max_execution_time.

You check this article on how to increase it or get in touch with your hosting provider to make the changes if its low.:
https://wpmudev.com/blog/increase-memory-limit/

Please do let us know how that goes.

Kind Regards,

Nithin

Hi Nithin,

Yes, the site is supposed to work in that way. The subdomain no.domain.dk hosts the Norwegian version of the site, managed by WPML.

The PHP memory limit is 1024M and the PHP time limit is 300.

Best Regards,
Peter

Hi @pstidsen

Based on our logs it seems that the scan is aborted after 12min and it seems that the memory limit and the PHP time limit are not only the two factors that have a place here. As mentioned in the previous reply there are too many server errors and BLC will stop the scan so it doesn’t put additional load on the server. It could be due to your low hosting plan, which has a low number of PCUs, RAM, and max_children.

Please consider switching to the Local(old) Engine and see if that gives some positive results.

Kind Regards,
Kris

Hi Kris,

Unfortunately, the local method does not work for me either, because some links in the database is giving 404, however the link is changed dynamically while loading the page and then the links works fine. Therefore, the cloud version is better because is looks at the links as they are front end.

It seems odd to me that the links are giving server errors because visiting them in the browser, everything is fine.

Best Regards,
Peter

Hi @pstidsen

I’m afraid, this looks more specific to how the server isn’t able to handle the load during the scan. However, I’m bringing this further to our team’s attention to see if there are any further aspects could be suggested.

Regards,

Nithin

Hi @pstidsen,

I’m afraid what could be done within the plugin side is limited as it’s more specific to the server load as mentioned before.

We did observe that the cache had expired for most pages, which can potentially lead to increased server load. Ensuring that all pages are appropriately cached and conducting multiple scans to ascertain whether the scans can retrieve cached pages could contribute to mitigating server load.

Optimizing the website and ensuring that all pages are cached efficiently should aid in enhancing the scanning process. However, this is only a workaround and you’ll have to check and see if the load in the server could be reduced in general to get the cloud version to run a scan successfully.

Kind Regards,

Nithin

Hi @pstidsen

I hope you are doing well.

We haven’t heard from you in a while, I’ll go and mark this thread as resolved. If you have any additional questions or require further help, please let us know!

Best Regards
Patrick Freitas