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: www.example.com
I ran this command:
It produced this output:
My web server is (include version): Nginx
The operating system my web server runs on is (include version): Centos 7
My hosting provider, if applicable, is:
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 situation is this:
Letsencrypt does not have a wildcard certificate. The home page of my website shows that the CA certificate is in the form of www.example.com. After the distribution certificate is issued by letsencrypt, I did not remove the previous CA certificate, but directly put /etc/letsencrypt/live The directory is directly renamed, and then apply for a wildcard certificate. After the configuration is successful, the home CA certificate of my website is in the form of *.example.com, but when renewing, he always reports the previous CA certificate error, and the wildcard certificate cannot be renewed normally!
And what I want to ask is, is direct certbot-auto delete completely solving this problem? If certbot-auto revoke, will the two identical domain names affect security issues?