I have certbot working properly using the set up below but I’m interested to know whether it’s possible to have a backup certificate provider as per Scott Helme’s article here.
While this probably seems overkill it raises an interesting point of reliance on Let’s Encrypt and what happens if they are offline for an extended timeframe.
As per the output below I get a warning that I already have a unexpired certificate for my domain and do I want to overwrite it, the answer to which is no I’d like a second certificate ideally stored in the same/similar location to my Let’s Encrypt certificates.
I’ve seen the options for
--config-dir would this be enough to separate the different directories or do I need a different machine with a clean setup for the other provider?
My domain is: clanrose.org.uk
It produced this output:
Plugins selected: Authenticator dns-cloudflare, Installer None
Cert not yet due for renewal
You have an existing certificate that has exactly the same domains or certificate name you requested and isn’t close to expiry.
My web server is (include version): nginx 1.15.5
The operating system my web server runs on is (include version): Ubuntu Server 18.10
My hosting provider, if applicable, is: Linode
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): certbot 0.28.0