SSL not working after 'successful' certbot install

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., 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:
sudo certbot --apache

It produced this output:
“Congratulations! You have successfully enabled

My web server is (include version):

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

My hosting provider, if applicable, is:
Google Cloud

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

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 0.31.0

I recently ran Certbot, and all seemed to go well, but the website is still running the old certificate, and not the Lets Encrypt one. I’m no Apache2 expert, but the site seems to be running using the 000-default.conf instead of 000-default-le-ssl.conf (which I guess was added by Certbot). Is that normal? If not, I guess that could be the probelm? Assistance here would be really appreciated.

Hi @wickywills

there is a check of your domain, ~~ one hour old -

You have created a new Letsencrypt certificate:

Issuer not before not after Domain names LE-Duplicate next LE
Let’s Encrypt Authority X3 2019-12-02 2020-03-01 - 1 entries duplicate nr. 1
AlphaSSL CA - SHA256 - G2 2019-05-14 2021-05-14 - 1 entries

But you use an expired Comodo EV certificate.

What says

apachectl -S

-bash: apachectl: command not found

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.