Hi @petebocken
Sorry to hear you are having this issue
Based on your description it is the Cloud scan, wouldn’t you mind let us know the domain so we can look into the logs?
Best Regards
Patrick Freitas
I’m seeing it on these two sites:
Hi @petebocken
candocanines.org
When it comes to Error 25 – Internal Request Timeout the scan of a link timed out and could not complete.
As for Error 21 – Internal Request Error the BLC could not complete the scan of the link.
Just in case, if there was some update on your server side, please whitelist our IPs and add BLC User Agent to allowlist
https://wpmudev.com/docs/wpmu-dev-plugins/broken-link-checker/#broken-link-checker-ip
https://wpmudev.com/docs/wpmu-dev-plugins/broken-link-checker/#broken-link-checker-user-agent
Also, can you share with us what, for both domains, what are those values:
- max execution time
- memory limit
Kind Regards,
Kris
Flywheel said they are not seeing anything get blocked for those IPs and/or user agent.
http://www.disability.state.mn.us is set to 256M and 300s timeout.
candocanines.org is set to 300M and 300s timeout.
I tested again on both sites and this time they both appear to actually scan (since it doesn’t just stop after 1 second). However, I still am getting “21 Internal Request Error” or “25 Internal Request Timeout” on both sites.
Hi @petebocken,
I checked the logs at our end, however, I was unable to notice any error with the scanning process. Can you please share a screenshot of the error that you observe at your end?
Please confirm if the Internal request error is showing up for external URLs. If yes, can you please share the URLs in your next response so that we can check this further?
Looking forward to hearing back from you and helping you diagnose the issue further.
Best Regards,
Nebu John
Yes, all links are external. Here are the CSV exports: https://share.zight.com/9ZuOqR1B
Hi @petebocken
I shared those logs with our BLC Team for review. We will post an update here as soon as more information is available.
Kind Regards,
Kris
Hi, i am getting error
21 Internal Request Error
Issue detail:
This indicates a general error and BLC could not complete the scan of the link
Can anyone please assist…
Thanks!
Hi @richir,
To ensure we can assist you in the best possible way, could you open a separate support topic that is specific to your website? This will help us focus on your particular case and provide the most relevant guidance.
https://ww.wp.xz.cn/support/plugin/broken-link-checker/#new-topic-0
Best Regards,
Nebu John
Hello @petebocken,
Please take our apologies for the delayed reply.
The issue might be caused by the requests being blocked by the server, if the Accept-Encoding header is missing.
We are currently still checking it with the developers, and will let you know once we have more feedback from them to share.
Best Regards,
Dmytro
Hello @petebocken,
In order to rule out possible plugin/theme conflicts, could you please check if you can perform the conflict test with the default theme enabled, and 3rd-party plugins deactivated, as explained here.
If the sites are live, it’s recommended to run such tests on a separate staging site, so that they don’t affect the live site appearance.
Best regards,
Dmytro
I cloned the site over to a dev server (mcd.westwords.dev), switched the active theme to Twenty Twenty-Five, ran the scan and it comes back with 500 Internal Server Errors, 25 Internal Request Timeouts, 21 Internal Request Errors, and 403 Forbiddens.
Hello @petebocken
Thank you for the update, I was able to check the BLC test results and the URLs reported.
The one URL reporting 500 Internal Server Error doesn’t look like an issue as when I try to load it, it shows me “There has been a critical error on the site” notice – which is why it is being reported as HTTP 500. Which is expected.
I also reviewed the 403 Forbidden URLs this can happen if the BLC User Agent and BLC IPs are unable to access the URL being reported. You can read more about it here: https://wpmudev.com/docs/wpmu-dev-plugins/broken-link-checker/#403-how-to-fix
Further, about the “25 Internal Request timeouts and 21 Internal Request Errors” I’ll share your update with our Devs so that they can take a deeper look and investigate further about it.
We’ll keep you posted as soon as we receive further information from them. Thank you for your patience while we are checking this further.
Kind Regards,
Saurabh
Hi @petebocken,
As we have already forwarded your update to our developers, and a fix for the issue is expected to be released with one of our upcoming updates, I am marking this thread as resolved, but if you have any additional questions, feel free to let us know.
Best Regards,
Nebu John
