• I’ve been trying the Broken Links Checker plugin for a few times over the years not, but I’m getting stuck on the same problem time after time. Broken Link Checker marks all links als broken (or technically as ‘Connection Failed”. All those links are good, but the log says this:

    Logboek: Failed to connect to https://www.wickedskakid.nl port 80: Connection refused [Error #7]

    I contacted my hosting provider to ask if they could whitelist the plugin, but they say the problem persists not due to a firewall setting but something else. I really don’t get what they try to tell me, but I still want to use this plugin. What to do?

    https://www.ads-software.com/plugins/broken-link-checker/

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter Ester Dammers

    (@rebelstar)

    Some additional information. The hoster asks if the maker of this plugin can tell me if and how the script can work with a local-loop http block. Don’t know what that is…

    Some additional information. The hoster asks if the maker of this plugin can tell me if and how the script can work with a local-loop http block. Don’t know what that is…

    Hmm, I’m afraid I’m not sure what that is either. It sounds like the hoster might be blocking scripts that run on your server from connecting back to that same server. Does that match what they told you?

    Of course, to check a link, the plugin must be able to connect to the server that the link points to. So if loopback connections are blocked, all internal links will show up as broken.

    In case the hosting provider asks, the plugin doesn’t do anything special with internal links vs. external links. It just sends a normal HTTP HEAD request for every link it checks.

    Thread Starter Ester Dammers

    (@rebelstar)

    Hi, thanks for the reply. This is what the hoster told me (I translated from Dutch to English)..

    Probably the script tries to connect to the own website, to collect data. This won’t be possible throughh http, the servers are not able to browse itself.

    When a script connects through http (like domain.com/filename.php), this won’t work. When it connects to a relative path (like ../filename.php), this will work.

    Maybe the maker of the script/plugin can indicatte how the script could work in case of a “local-loop http block”

    Because the script works like looking up through the URL if links or files are accessible, this probably can’t be changed. A setting like this won’t work on our servers, unfortunately.

    Unfortunately, it sounds like there’s nothing I can do. If the hoster doesn’t let scripts connect to the site via HTTP, the plugin can’t check internal links.

    When it connects to a relative path (like ../filename.php), this will work.

    That suggestion wouldn’t work in this case as WordPress posts/pages/etc are not actual files on disk. They’re database entries mapped to specific URLs.

    All I can recommend is adding your domain name to the exception list in Settings -> Link Checker -> Which Links To Check. This will stop the plugin from trying to check internal links. It will still check links from your site to other sites.

    Thread Starter Ester Dammers

    (@rebelstar)

    Thanks for replying again. I did add my domain to exceptions, but that doesn’t change the fact that the plugin still reports good external links as bad.

    Does it report the same error for external links, or something different?

    Thread Starter Ester Dammers

    (@rebelstar)

    Yes, it’s exactly the same error (connection refused)

    Interesting. It’s still probably server-related as I added the link you posted earlier (https://www.wickedskakid.nl/) to a test site and BLC correctly identified it as working.

    Thread Starter Ester Dammers

    (@rebelstar)

    Sorry for my very late reply. My hoster says everything is normal, but probably there’s still a block somewhere. Thanks for your help anyway.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘All links identified as broken’ is closed to new replies.