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.
I ran this command: sudo certbot -d $DOMAIN -d $WILDCARD --manual --preferred-challenges dns certonly
It produced this output:
You have an existing certificate that has exactly the same domains or certificate name you requested and isn’t close to expiry.(ref: /etc/letsencrypt/renewal/samuelsandoval.net.conf)
What would you like to do?
1: Keep the existing certificate for now
2: Renew & replace the cert (limit ~5 per 7 days)
My web server is (include version): Wordpress Lightsail Instance
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is: Amazon Lightsail
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 version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot
Please show the output of sudo certbot certificates.
This message suggests the certificate you are trying to create may not be close to renewal date (which means 30 days before expiry).
In case you are wondering why you created two certificates in the past days and it still doesn't work. You are running certonly, reload your Apache webserver.
P.S. certonly means it'll only create the certificate, not responsible for adding it to webserver.