# Confirm ACME2 switch (how to)

**URL:** <https://community.letsencrypt.org/t/confirm-acme2-switch-how-to/113008>\
**Category:** Help\
**Created:** [February 12, 2020, 5:45pm UTC](https://community.letsencrypt.org/t/confirm-acme2-switch-how-to/113008 "2020-02-12T17:45:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![lancedolan](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/lancedolan/32/16982_2.png) [@lancedolan](https://community.letsencrypt.org/u/lancedolan)\
**Post date:** [February 12, 2020, 5:45pm UTC](https://community.letsencrypt.org/t/confirm-acme2-switch-how-to/113008/1 "2020-02-12T17:45:28Z")

</div>

We _believe_ we've completed our upgrade to an ACME2 client, however we want a surefire guaranteed way to confirm that we're not still accidentally using ACME1 under the hood.

After the upgrade, our new certbot version is...

```nohighlight
$ certbot --version
certbot 0.31.0

```

We've already successfully created and installed certs with the new client. How can we confirm beyond the shadow of any doubt that we're using ACME2 under the hood, not ACME1, and that we won't be surprised and S.O.L. come June 1st?

There must be some quick command to check. I used the `-v` toggle and saw lines like the following:

```nohighlight
Sending GET request to https://acme-v02.api.letsencrypt.org/directory.

```

So, I'm fairly confident we're good to go, but I want _absolute_ confidence.

Some of the usual info asked....

> I ran this command:  
> certbot certonly --webroot --csr /path/to/my.csr -w /path/to/my/webroot -d domain1 -d domain2 (etc etc)

> It produced this output:  
> the usual successful message about a successful cert

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

> I can login to a root shell on my machine (yes or no, or I don't know):  
> Yes

---

<div class="post-metadata">

**Author:** ![lancedolan](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/lancedolan/32/16982_2.png) [@lancedolan](https://community.letsencrypt.org/u/lancedolan)\
**Post date:** [February 12, 2020, 5:49pm UTC](https://community.letsencrypt.org/t/confirm-acme2-switch-how-to/113008/2 "2020-02-12T17:49:10Z")

</div>

Note: I had expected to end up with a newer version than certbot 0.31.0. I believe 1.1.0 is out. I followed the instructions on [https://certbot.eff.org/](https://certbot.eff.org/) exactly. If you see a major issue with using this version, please let me know, otherwise I’m continuing with this.

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [February 12, 2020, 6:54pm UTC](https://community.letsencrypt.org/t/confirm-acme2-switch-how-to/113008/3 "2020-02-12T18:54:28Z")

</div>

Hi @lancedolan

> [@lancedolan](#):
>
> acme-v02.api

check your log if there is an `acme-v01.api...` - order.

If not, the job is done.

---

<div class="post-metadata">

**Author:** ![ZetaRevan](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/zetarevan/32/37496_2.png) [@ZetaRevan](https://community.letsencrypt.org/u/ZetaRevan)\
**Post date:** [February 13, 2020, 4:16am UTC](https://community.letsencrypt.org/t/confirm-acme2-switch-how-to/113008/4 "2020-02-13T04:16:11Z")

</div>

> [@lancedolan](#):
>
> I had expected to end up with a newer version than certbot 0.31.0. I believe 1.1.0 is out.

It is, but not necessarily in the repos just yet. You'd need to manually get it & install it.

---

<div class="post-metadata">

**Author:** ![lancedolan](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/lancedolan/32/16982_2.png) [@lancedolan](https://community.letsencrypt.org/u/lancedolan)\
**Post date:** [February 13, 2020, 4:05pm UTC](https://community.letsencrypt.org/t/confirm-acme2-switch-how-to/113008/5 "2020-02-13T16:05:29Z")

</div>

It appears we’re good to go. Thank you for curing our paranoia!

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [March 14, 2020, 4:05pm UTC](https://community.letsencrypt.org/t/confirm-acme2-switch-how-to/113008/6 "2020-03-14T16:05:40Z")

</div>

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