I have the same issue.
I like the idea of checking links but having the plug-in say internal are bad is misleading and time wasting.
This turned out to be a server/DNS(IP) configuration error, and not the plugins fault.
kingkong954,
I’ve started having the same issue. Recently migrated blog to another server and also dns provider. I’m curious what server/DNS(IP) issues you stumbled across.
Any feedback would be much appreciated.
Thanks,
Robert
The IP our server was given was placed in an aggressive firewall zone that didn’t allow it to receive/transmit certain types of data. Once we gave it a more liberal zone, the plugin worked.
Thanks @kingkong954,
That put me on the right track and I found the issue. In my case – firewall was not accepting pings on internal interface.
Cheers,
Robert
kingkong954,
Think I jumped victory too soon.
Even after opening up ping traffic on the fireall – I’m still getting…
1. Log : couldn’t connect to host [Error #7]
=== (No response) ===
Link is broken.
——————-
I recently moved my blog from shared hosting to a cloud server. I therefore have full control over the environment. Wonder what I can try next?
Any ideas?
Robert
We SSH’d into the server, and tried to get it to ping out to external servers, and see if it could receive data back. It couldnt.
See if yours can.
kingkong954,
Very odd. SSH’d in – like you suggested. Was able to ping external addresses but not my own! Iptables flushed and firewall shutdown – still not able to ping self. So decided to reboot – guess what? Working like charm!
Broken Link Checker working like charm.
Thanks for giving me ideas to keep looking.
Cheers,
Robert
