Invalid cert for domain after changing DNS

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: i used the certbot script to generate a new certificate for my new domain (before it was and now it is, the script says it was successful but when I access the new dns it says it is insecure. i think it is still running the fake cert.

It produced this output: says it is not secure

My web server is (include version): nginx (LTS)

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

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): i am using the docker certbot image.

That’s exactly what’s happening:
Re-run certbot without telling it to use the staging server, and you should be set.

1 Like

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