Ssl: certificate_verify_failed

Help
1

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: aaasv-cistest-d002.internal.app3as-cloud.local

I ran this command: certbot certonly --standalone -d aaasv-cistest-d002.internal.app3as-cloud.local

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log

An unexpected error occurred:

requests.exceptions.SSLError: HTTPSConnectionPool(host='pki.3as-cloud.com', port=443): Max retries exceeded with url: /acme/ (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1131)')))

My web server is (include version):

The operating system my web server runs on is (include version): Ubuntu 20.04.6

My hosting provider, if applicable, is: no idea

I can login to a root shell on my machine (yes or no, or I don't know): yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 2.10.0

2

You aren't ever going to get a Let's Encrypt certificate for anything under the local TLD. Let's Encrypt only issues certificates for valid public hostnames and local is not a public TLD. It is reserved for use with mDNS.

Any FQDN in the certificate request must resolve in public DNS.

3 Likes
3

Looks like they're running their own ACME server at pki.3as-cloud.com (which is not an existing hostname on the public DNS, probably internally too?)

I'm guessing their internal ACME server at pki.3as-cloud.com also uses a certificate from their own CA, but that private CAs root certificate isn't trusted by the host running Certbot.

But that's only guessing due to a lack of information.

4 Likes