Renewal/example.com.conf file?

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.

My domain is: logi.angazadesign.com

I ran this command: certbot certificates

It produced this output: No certs found. Background: We created the cert on an ephemeral EC2 instance and copied it over without copying over /etc/letsencrypt/renewal/logi.angazadesign.com.conf . When I step through certbot with a debugger, cert_manager.py:certificates() calls storage.renewal_conf_files(config) and of course finds nothing. Rather than painstakingly reverse-engineer the contents of that file, I’d love it if someone can point me to an example. Thanks!

My web server is (include version): Logi Composer

The operating system my web server runs on is (include version): Ubuntu 18.0.4

My hosting provider, if applicable, is: n/a

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): 0.27.0

1 Like

What’s your goal?

It’s unlikely that you can just restore the old .conf file. Its contents is intertwined with the directory structure and contents of /etc/letsencrypt/{accounts,archive,live}. If you’re missing any needed files or have messed up any of the symlinks, Certbot will crash in unexpected ways.

I would guess that starting from scratch is a safer and easier thing to do.

Unrelated, but or Ubuntu 18.04, you should install Certbot from the PPA, which is slightly newer and has some important bug fixes: https://certbot.eff.org/lets-encrypt/ubuntubionic-other

2 Likes

Our goal is to renew. We’ll start clean. Thanks so much!

2 Likes