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:
I ran this command:
sudo certbot certonly -v --manual --manual-public-ip-logging-ok --email --agree-tos --domain jojocommunication.com --rsa-key-size 2048 --config-dir .jojo --work-dir .jojo --logs-dir .jojo
It produced this output:
Saving debug log to /Users/sam/.jojo/letsencrypt.log
Plugins selected: Authenticator manual, Installer None
Certificate is due for renewal, auto-renewing...
Renewing an existing certificate for jojocommunication.com
Performing the following challenges:
http-01 challenge for jojocommunication.com
Create a file containing just this data:
And make it available on your web server at this URL:
Press Enter to Continue
Waiting for verification...
Cleaning up challenges
Successfully received certificate.
Certificate is saved at: /Users/sam/.jojo/live/jojocommunication.com/fullchain.pem
Key is saved at: /Users/sam/.jojo/live/jojocommunication.com/privkey.pem
This certificate expires on 2023-09-07.
These files will be updated when the certificate renews.
- This certificate will not be renewed automatically. Autorenewal of --manual certificates requires the use of an authentication hook script (--manual-auth-hook) but one was not provided. To renew this certificate, repeat this same certbot command before the certificate's expiry date.
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
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
A Small Orange shared hosting service
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
yes, cpanel 94.0.25. Using "SSL/TLS Status" menu, viewing existing certificate and selecting upgrade. Copying fullchain.pem to "Certificate (CRT)" results in "The certificate is not valid".
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
certbot 2.3.0 installed using brew on a Mac; upgraded to 2.6.0 with the same result, less the website challenge and an indication that --manual-public-ip-logging-ok was no longer required.
I'm just not sure where to go to next given I've followed this process before and not had issues. Any help gratefully received. I'm sure I've done something simple wrong...