Updating certbot 0.23 to 0.31 automactiycally force use of acme v2?

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:
nomura.ca

I ran this command:
sudo apt-get install certbot

It produced this output:
installed certbot 0.31

My web server is (include version):
HAProxy

The operating system my web server runs on is (include version):
Ubuntu 18.04 LTS
My hosting provider, if applicable, is:

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.23

I’ve seen conflicting information. So I ask the question here. Sorry if it has been covered before but I can’t find it. The official docs say “usually” nothing else needs to be done but how can I be sure? I haven’t done the 0.31 upgrade on production yet. I’ve done this upgrade to 0.31 on dev and was wondering if there’s a way to tell if acme v1 or v2 was used after the fact.

Does upgrading the client form 0.23 to 0.31 automatically force use of acme v2?

Regards,
Victor

1 Like

I don’t think that 0.31 can’t do acmev1, so I would have to say no, acmev2 use is NOT forced by 0.31 - however, it may be the preferred/default choice.
0.31 can do acmev1 and acmev2; whereas I think 0.23 can only do acmev1.

If you are looking for a test to confirm acmev2 use, try a --dry-run against the current staging environment (which is set to only do acmev2).

1 Like

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