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: dreadstar.net
I ran this command: sudo certbot certonly --manual --manual-public-ip-logging-ok --preferred-challenges dns-01 --server https://acme-v02.api.letsencrypt.org/directory -d "*.dreadstar.net" -d dreadstar.net
It produced this output:
Congratulations! Your certificate and chain have been saved at:
Your key file has been saved at:
Your cert will expire on 2021-08-25. To obtain a new or tweaked
version of this certificate in the future, simply run certbot
again. To non-interactively renew all of your certificates, run
If you like Certbot, please consider supporting our work by:
My web server is (include version): apache 2.4.29 64-bit
The operating system my web server runs on is (include version): Ubuntu 18.04
My hosting provider, if applicable, is: n/a
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): certbot 0.31.0
I have a wildcard cert that seems to flip-flop back and forth between two directories every time I renew them.
One directory just has the name dreadstar.net and the other is dreadstar.net-0001 . When my apache config is set to use dreadstar.net, when I renew the wildcard cert, it renews dreadstar.net-0001 . Then I configure apache to use the -0001 directory, and when I renew it, it renews. the dreadstar.net directory.
How do I get rid of the -0001 directory and just have one directory for my wildcard cert?
Also, when I try to add the Nextcloud server for my calendar and contacts, it tells me the cert expired back in 2018. But when I check it form my Mac, Windows or Linux machines, it shows a valid cert that expires in July.