Comment 3 for bug 1885585

Same problem here,

because: Connection skipped because the server doesn't have a valid HTTPS certificate. It will be retried on the next probing run.

http://launchpadlibrarian.net/667961958/mirror.hnd.cl-archive-probe-logfile.txt

But our mirror have a valid and working certificate

https://mirror.hnd.cl/ubuntu/

% nmap --script ssl-cert -p 443 mirror.hnd.cl
Starting Nmap 7.93 ( https://nmap.org ) at 2023-05-25 23:21 -04
Nmap scan report for mirror.hnd.cl (138.186.10.35)
Host is up (0.0035s latency).
rDNS record for 138.186.10.35: 35.10.186.138.static.hostednode.net

PORT STATE SERVICE
443/tcp open https
| ssl-cert: Subject: commonName=mirror.hnd.cl
| Subject Alternative Name: DNS:mirror.hnd.cl
| Issuer: commonName=R3/organizationName=Let's Encrypt/countryName=US
| Public Key type: rsa
| Public Key bits: 2048
| Signature Algorithm: sha256WithRSAEncryption
| Not valid before: 2023-04-15T23:36:34
| Not valid after: 2023-07-14T23:36:33
| MD5: 525fad578a5ecc3e5b0f2fd00cfc4399

nmap -6 --script ssl-cert -p 443 mirror.hnd.cl

Starting Nmap 6.40 ( http://nmap.org ) at 2023-05-25 23:23 -04
Nmap scan report for mirror.hnd.cl (2803:8240:50:1035::35)
Host is up (0.11s latency).
PORT STATE SERVICE
443/tcp open https
| ssl-cert: Subject: commonName=mirror.hnd.cl
| Issuer: commonName=R3/organizationName=Let's Encrypt/countryName=US
| Public Key type: rsa
| Public Key bits: 2048
| Not valid before: 2023-04-15T23:36:34+00:00
| Not valid after: 2023-07-14T23:36:33+00:00
| MD5: 525f ad57 8a5e cc3e 5b0f 2fd0 0cfc 4399
|_SHA-1: 6d05 e390 16c3 9321 547d fbcb 7298 72c7 8b17 d1b6

Nmap done: 1 IP address (1 host up) scanned in 1.51 seconds
|_SHA-1: 6d05e39016c39321547dfbcb729872c78b17d1b6