Most (all?) https checks fail with "Unknown error" and "=== (No response) ==="

  • Resolved solarbird

    (@solarbird)


    8 years, 10 months ago

    Hi! For the last three weeks (notably since restarting our server on Debian Jessie) all link verification requests involving https have been failing. All report “Unknown error” as the cause with Log: === (No response) === and 0.000 response time. Here is a screenshot; all the errors look the same:

    https://solarbird.net/Livejournal/2016-02/https-failures.gif

    I suspect but do not know that all https:-linked checks are failing; we are currently seeing 1322 bad links, and it’s too many to troll through.

    I know that the latest version of OpenSSH has caused all sorts of problems, but this has been going on since before the problem version was released (albeit by only a week or so), so I don’t think that’s it. I didn’t find anything obvious poking around, and I do have the latest versions, and specifically checked to make sure I have the GET/HEAD patch discussed on this forum earlier. (Patch released two weeks ago.)

    Given that I am not seeing this discussed more widely, I am suspecting we have a local issue, but I have not seen anything useful in searches to tell me what that issue might be.

    For completeness: http-headed links verify correctly. We are able to use ssh on the server to communicate with other servers, and ssl-based utilities such as scp also all work correctly.

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

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter solarbird

    (@solarbird)

    I neglected to specify: this is happening across multiple installs, both network and standalone, but all on the same server.

    I am seeing the same problem, all my https links. I manually checked 25 links and they all work just fine. I did just upgrade to PHP7 which might influence things

    I am experiencing the same problem after we installed a SSL certificate and redirected all our http traffic to https.

    I tried to delete the plugin and reinstall, but no luck either.

    I am hoping for a fix ?? thanks!

    Thread Starter solarbird

    (@solarbird)

    It is still failing here even though we are on php5. It does say that it is using snoopy (as above) which comments on another thread indicated will always fail on https. But we have php5-curl and libcurl3 installed, so I don’t know what’s up with that either.

    I mean, at the moment, it’s completely useless and I’ve disabled special formatting because I have over 1300 links falsely tabbed as broken across five years of blog entries.

    Thread Starter solarbird

    (@solarbird)

    Okay, I may have it dealing with curl again and have restarted the plugin from scratch and we appear to be behaving better so far. So make sure you have curl installed and apache dealing with it sensibly, then deactivate/re-activate the plugin and force-recheck all links. Make sure in the debug menu at that point that it’s actually using curl and not snoopy.

    Thread Starter solarbird

    (@solarbird)

    Okay, yeah, we had curl libs all installed but for some reason it turns out that (surprise!) apache wasn’t dealing with it correctly. We’ve got apache to pay attention and now have functionality restored. (This was not the top of our queue, which put it off for weeks.)

    Anyway, anyone else watching this thread may want to know that if you are using snoopy instead of curl to detect broken links, all https queries will fail. Get curl working.

    If curl is working, and the plugin sees it, you have a different problem.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Most (all?) https checks fail with "Unknown error" and "=== (No response) ==="’ is closed to new replies.