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.
It produced this output: - Congratulations! Your certificate and chain have been saved at:
/etc/letsencrypt/live/kofcchap6ca.org/fullchain.pem
Your key file has been saved at:
/etc/letsencrypt/live/kofcchap6ca.org/privkey.pem
Your cert will expire on 2021-04-07. 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
"certbot renew"
==> Issue: Can't find any of the files for the SSL in /etc/letsenc.. directory as defined in the msg.
My web server is (include version): Apache Version 2.4.46
The operating system my web server runs on is (include version): Apache Version 2.4.46
My hosting provider, if applicable, is: GoDaddy Hosting Package Deluxe
I can login to a root shell on my machine (yes or no, or I don't know): No
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
cPanel Version 86.0 (build 30)
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 0.40.0
My burning question:
How did you manage to install certbot on a GoDaddy shared hosting account? As the resident GoDaddy guy, I am most intrigued by this.
I was working with an article: https://cyberblogspot.com/how-to-get-a-free-ssl-certificate-for-godaddy/
that provided me with the steps needed to install SSL certificates on a GoDaddy Shared account. I don't have root access so I created the envir. needed on my windows 10 pro pc. I managed to get the latest copy of "Certbot" up and running. I launched from the cmd prompt the Linux terminal by running "bash"
I successfully ran 'certbot' manually, created the file directed and uploaded it to the website root as directed. This was needed to verify my domain.
I was then able to successfully create the SSL certificates as displayed by 'certbot' :
Congratulations! Your certificate and chain have been saved at:
I just read your message to Osiris that answers many of my questions. I've read your website's certificate history and ran several tools, so I'm more than happy to help you through this. It would be much easier if you came back to the forum though so as not to get confusing message fragments.
The reason that you can't find the certificate and private key files in live is because they're symbolic links and not real files. You need to look in archive for the real files.
I didn't. I created the envir. needed on my Windows PC and ran the
"certbot" manually. I created the file needed on the server and copied it
over to the server. Once this was done I completed the request to get the
SSL certificates and "certbot" reported that it successfully did so. Here
is that mgs received from "certbot" as displayed on the local terminal
running on my local pc:
- Congratulations! Your certificate and chain have been saved at: /etc/letsencrypt/live/kofcchap6ca.org/fullchain.pem
Your key file has been saved at: /etc/letsencrypt/live/kofcchap6ca.org/privkey.pem
Your cert will expire on 2021-04-07. 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 "certbot renew"
So, this dummy when over to the server and looked in the /etc/ directory
for the files so that they could be copied and used on the CPanel SSL
management screen.
No, I was working on my meeting for tonight and will need to table this until morning. I just received notification that my test.kofc... certificate has already expired. I knew this and not worried about it as it is simply my test machine. My outstanding question is, where do I find that archive folder to locate the real files that were generated by certbot?
By the way, thanks a whole bunch for your feedback. I will pick this up in the moring.
Lou
