I would check the expiration and names used (public.pem).
If useful, you could pickup where that left off.
If not useful, then delete and start from scratch.
Thanks rg - I deleted and cloned OK, then -
at the ‘Help Install File’ step
$ ./letsencrypt-auto --help
"sudo" is not available, will use “su” for installation steps…
Sorry, I don’t know how to bootstrap Certbot on your operating system!
I went to that page and could not find any specific directions.
I am on GoDaddy, w/ a shared hosting at the moment, C-Panel etc., and a Linux O/S as mentioned earlier from a ‘uname -a’ output.
Certbot is usually not very appropriate for shared hosting (at least, the default options and behaviors require root access). A number of earlier GoDaddy threads here had people seemingly in a similar situation to yours:
I do have root access.
At least I can log in as a user w/ root privilege, into a bash shell, using PUTTY, perform typical activity as outlined in previous postings. So far regular UNIX type commands are read, accepted and interpreted.
???
I created https://github.com/certbot/certbot/issues/4806 to track improving that link. To give you the information here though, you need the following software installed on your OS to use Certbot:
Python 2.6, 2.7, or 3.3+ and its header files
virtualenv
gcc
Augeas
openssl command line tool and headers
foreign function interface library
Usually you would install this software through a tool like apt-get, yum, or dnf.