Mirror prober incorrectly reports an invalid SSL certificate

Bug #1885585 reported by NetActuate Ops on 2020-06-29
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Undecided
Unassigned

Bug Description

We have been noticing a problem with the mirror probing where partway through the probe, it suddenly starts complaining about our mirror having an invalid certificate, which is absolutely not the case.

https://launchpad.net/ubuntu/+mirror/mirror1.cl.netactuate.com-archive
https://launchpad.net/ubuntu/+mirror/mirror1.cl.netactuate.com-release

Here are logs with the failures:
http://launchpadlibrarian.net/486354226/mirror1.cl.netactuate.com-archive-probe-logfile.txt
http://launchpadlibrarian.net/486330936/mirror1.cl.netactuate.com-release-probe-logfile.txt

As you can see from the logs, everything starts off fine, then suddenly one check claims there is an invalid HTTPS certificate, and everything else gets skipped.

You can also see here where everything worked fine:
http://launchpadlibrarian.net/486109160/mirror1.cl.netactuate.com-archive-probe-logfile.txt
http://launchpadlibrarian.net/486094033/mirror1.cl.netactuate.com-release-probe-logfile.txt

Nothing has changed with the certificate between these probes.

"Invalid SSL certificate" can also mean a lot of different things specifically, having more verbose logs of such a failure would be useful.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers