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:walkershire.net
I ran this command: certbot renew
It produced this output:
My web server is (include version): Apple Mini
The operating system my web server runs on is (include version):
MACOS Monerey 12.6
My hosting provider, if applicable, is:my company server on Comcast Business
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):1.30.0
I have several domains with LetsEncript certificates which were installed about July 10, 2022. I tried to renew them on September 20 but had the --apache-bin is missing error and the PluginError('Unable to create a lock file in /etc/apache2.”. I found a fix by Griffin on Community.LetsEncript and tried it. The response said the it was successful with a mid December expiration date. I later checked the certificates expiration by clicking on the lock icon using a browser which showed Saturday, October 8, 2022 at 2:22:19 PM.
Today I reinstalled Apache and then CertBot version 1.30.0 using Brew. Then ran certbot renew and got the same apache-bin and PluginError as before.
Ran Griffins ‘ certbot certonly --webroot -w /path/to/webroot/for/www.sobco.com -d "www.sobco.com" --dry-run ‘. Log shows:
The dry run was successful.
lowerlevel@70-89-220-117-clean-air-engineering-il ~ % certbot certonly --webroot -w /usr/local/var/www/walkershire -d "www.walkershire.net"
Saving debug log to /usr/local/etc/certbot/logs/letsencrypt.log
Certificate not yet due for renewal
You have an existing certificate that has exactly the same domains or certificate name you requested and isn't close to expiry.
What would you like to do?
1: Keep the existing certificate for now
2: Renew & replace the certificate (may be subject to CA rate limits)
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
Renewing an existing certificate for www.walkershire.net
Successfully received certificate.
Certificate is saved at: /usr/local/etc/certbot/certs/live/www.walkershire.net/fullchain.pem
Key is saved at: /usr/local/etc/certbot/certs/live/www.walkershire.net/privkey.pem
This certificate expires on 2022-12-31.
These files will be updated when the certificate renews.
- The certificate will need to be renewed before it expires. Certbot can automatically renew the certificate in the background, but you may need to take steps to enable that functionality. See User Guide — Certbot 1.30.0 documentation for instructions.
If you like Certbot, please consider supporting our work by:
Donating to ISRG / Let's Encrypt: Donate - Let's Encrypt
Donating to EFF: Support EFF's Work on Let's Encrypt | Electronic Frontier Foundation
lowerlevel@70-89-220-117-clean-air-engineering-il ~ %
But the browser locks shows October 8, 2022 at 2:22:19 PM because they are not using the www certificate folder.
1st created 5 certificates for the plain domain names:
2022-07-18 17:31:36,150:DEBUG:certbot._internal.display.obj:Notifying user: Found the following certs:
Certificate Name: walkershire.net
Later with late night help from rg305(who is very good) on my CaptainBill log Challenges Failed Due To Invalid Response From .well-known I created the 11 domain certificates as can be seen at the bottom of this thread.
What should I do to get all 11 certificates renewed ?