Hardware problem with old server - key not backed up

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: westnab.com (currently down - hardware failure)

I ran this command: (I haven’t yet)

It produced this output:

My web server is (include version): apache2 2.4.29 on different hardware

The operating system my web server runs on is (include version): ubuntu server 18.04.4 on different hardware

My hosting provider, if applicable, is: self

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): not installed yet

My web server is down because of a serious hardware fault. I have built a LAMP stack on another machine and starting to configure. Am I right in thinking that I should have backed up the certificate key in case of just such a situation and that it will be difficult to create a certificate for the domain without the key file? If so what do I need to do? Or can I just create a new certificate?

1 Like

Creating a new certificate is absolutely fine. Let’s Encrypt has rate limits, so you can’t create tons of new certificates, though.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.