BLC 2.0 Fails to initialize on HTTPS sites using a self-signed certificate

  • Resolved davidginzberg

    (@davidginzberg)


    7 months, 1 week ago

    Broken Link Checker 2.0 fails to initialize the cloud scanner on sites that use HTTPS with a self-signed certificate. When the failure occurs no information is provided in the dashboard other than a recommendation to whitelist the IPs and UA string (which does not fix the problem).

    Using the curl command curl --header quickly identifies the problem, and establishing a non-self-signed certificate fixes it, but most users will have no hint that they need to do that.

    Please add information to the documentation indicating that SSL certificates that are self-signed will not work, and if possible add an indication in the error message that the cause was a certificate error (it would be better to support self-signed certificates if possible, but I realize that might be a big lift).

    The site listed above no longer has a certificate issue, so it will not be useful for testing the issue, but if the WPMU DEV team’s logs from 1-2 weeks ago are still available there may be some useful diagnostic information there.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Nebu John – WPMU DEV Support

    (@wpmudevsupport14)

    Hi @davidginzberg,

    I hope you are keeping well and thank you for reaching out to us.

    We have brought this to the notice of the BLC team for further review. We’ll update you here once we have feedback on this as soon as possible.

    Kind Regards,
    Nebu John

    Thread Starter davidginzberg

    (@davidginzberg)

    Hello Nebu,

    Thank you for your response. I will keep an eye on this topic for a follow-up once the BLC team has had time to assess.

    Thanks,
    David

    Plugin Support Kris – WPMU DEV Support

    (@wpmudevsupport13)

    Hi @davidginzberg

    Our BLC Team made a review of this and we have already made an improvement task for them which will make sure that an appropriate error message will appear if this error occurs we will also add info about this in our docs. Please note we do not have any ETA when this will be implemented.

    Kind Regards,
    Kris

    Thread Starter davidginzberg

    (@davidginzberg)

    Hi Kris,

    Thank you for the update. It’s good to know that the BLC team is planning to address the issue.

    I am reverting the “resolved” flag until the feature you described is released to production and/or the issue is listed in the troubleshooting section of the docs. Looking forward to seeing that release.

    Cheers,

    David

    Hi @davidginzberg ,

    Implementing a fix in our services is not a straightforward task. It requires careful evaluation, planning, and development to ensure that it meets our quality standards as well as the specific needs of our users. We need to consider various factors such as technical feasibility, compatibility, and potential impact on existing functionalities.

    While we cannot provide you with an exact timeline for implementation at this point, please be assured that our team is always working on improving our BLC Cloud service.

    Having explained that I’ll mark this thread as resolved. Note that you can still reply on this topic, additionally, you can also subscribe to our Roadmap to get updates on this link https://wpmudev.com/roadmap/#upcoming-broken-link-checker-2-4

    If you have any additional questions or require further help, please let us know!

    Best regards,
    Laura

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘BLC 2.0 Fails to initialize on HTTPS sites using a self-signed certificate’ is closed to new replies.

Tags