Invalid certificate

#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. https://crt.sh/?q=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:

I ran this command:

It produced this output:

My web server is (include version): aws lightsail - bitnami

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

My hosting provider, if applicable, is: aws

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): no

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

After installing my certificate I am getting invalid cert. I rebooted the apache server, tried updating the cert but the issue persists.

Thanks.

#2

Hi @skk

there is no certificate installed.

You have created one certificate. But it looks this is the first time ( https://check-your-website.server-daten.de/?q=poolforcellc.com ):

CertSpotter-Id Issuer not before not after Domain names LE-Duplicate next LE
907007657 CN=Let’s Encrypt Authority X3, O=Let’s Encrypt, C=US 2019-05-12 04:30:39 2019-08-10 04:30:39 poolforcellc.com, www.poolforcellc.com
2 entries duplicate nr. 1
586923480 CN=Amazon, OU=Server CA 1B, O=Amazon, C=US 2018-10-16 00:00:00 2019-11-16 12:00:00 www.poolforcellc.com
1 entries
586923481 CN=Amazon, OU=Server CA 1B, O=Amazon, C=US 2018-10-16 00:00:00 2019-11-16 12:00:00 www.poolforcellc.com
1 entries

I ran this command:

It produced this output:

If you use bitnami, there are additional steps required to install the certificate certbot has created.

Check the documentation. There are a lot of different bitnami configurations.

#3

Looks like there is a certificate present.

#4

Hi @skk,

certonly means “obtain the certificate and save it to disk, but don’t reconfigure any web server application to use it”.

Therefore, your certificate does exist on disk and is ready to be used—by editing web server application configuration files, such as an Apache configuration, to tell them to use the certificate chain and key, and where to find them.