Hi @yorkslad12
Thank you for response!
As for the example links and their details – yes, that was what I was after.
The error (or rather a warning) that you are seeing in logs is not the cause but a consequence of this. The specific line is meant to check and handle HTTP response code. As the details show
http code 0, log === (No response) ===
it means that the attempt to check given link – the HTTP request to the URL – actually get no response at all.
I admit this is a bit strange. It is known issue that some of the services (especially e.g. behind CloudFlare or belonging to some big services that have a very strict “anti-bot” or “anti-crawl” policy; a strict access control in general) would block such checks but that should usually result in HTTP responses such as “403 forbidden” or similar and not no response at all.
Given the fact that there’s also the same “no response” result from your own site, I suspect that there’s some other aspect involved but I’m not sure yet what.
You mentioned that it all started at some point.
Were there some updates made to the site or changes in some security settings? Is the site using some kind of security/firewall plugin (and if yes what is it) and/or is there some additional firewall similar security layer at the server level (and if yes, what is it)?
Kind regards,
Adam