# Get ISRG Root X2

**URL:** <https://community.letsencrypt.org/t/get-isrg-root-x2/174887>\
**Category:** Help\
**Created:** [March 31, 2022, 2:44pm UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887 "2022-03-31T14:44:24Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![GodSir](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@GodSir](https://community.letsencrypt.org/u/GodSir)\
**Post date:** [March 31, 2022, 2:44pm UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/1 "2022-03-31T14:44:25Z")

</div>

i want to try use ISRG Root X2 for EC cert. how i do it? i had using Certify The Web tool setup it, but it can't get ISRG Root X2 cert.

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [March 31, 2022, 2:51pm UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/2 "2022-03-31T14:51:16Z")

</div>

Read here:

> [@ECDSA availability in production environment](https://community.letsencrypt.org/t/ecdsa-availability-in-production-environment/150679):
>
> W…

and be prepared to wait.

---

<div class="post-metadata">

**Author:** ![GodSir](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@GodSir](https://community.letsencrypt.org/u/GodSir)\
**Post date:** [March 31, 2022, 3:43pm UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/3 "2022-03-31T15:43:54Z")

</div>

i can't find my account id, my using tools has no any logs about it.

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [March 31, 2022, 4:05pm UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/4 "2022-03-31T16:05:38Z")

</div>

That would have to be something you'll have to sort out with the support of the ACME client you're using. Or provide more info about your ACME client, perhaps anyone here knows something about it.

---

<div class="post-metadata">

**Author:** ![webprofusion](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/webprofusion/32/85310_2.png) [@webprofusion](https://community.letsencrypt.org/u/webprofusion)\
**Post date:** [April 1, 2022, 4:47am UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/5 "2022-04-01T04:47:22Z")

</div>

You should direct this question to [https://community.certifytheweb.com](https://community.certifytheweb.com) but you will find your account id as part of the managed certificate log file [which you can find on the status tab of any managed certificate you have already set up].

---

<div class="post-metadata">

**Author:** ![GodSir](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@GodSir](https://community.letsencrypt.org/u/GodSir)\
**Post date:** [April 1, 2022, 12:38pm UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/6 "2022-04-01T12:38:51Z")

</div>

The Certify has no any about account id information.

---

<div class="post-metadata">

**Author:** ![GodSir](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@GodSir](https://community.letsencrypt.org/u/GodSir)\
**Post date:** [April 1, 2022, 12:49pm UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/7 "2022-04-01T12:49:24Z")

</div>

> [@Osiris](#):
>
> ve to be something you'll have to sort out with the support of the ACME client

i using pfsense 2.6 and [certifytheweb.com](http://certifytheweb.com)

---

<div class="post-metadata">

**Author:** ![GodSir](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@GodSir](https://community.letsencrypt.org/u/GodSir)\
**Post date:** [April 1, 2022, 2:02pm UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/8 "2022-04-01T14:02:20Z")

</div>

mybe i find account such as:

[https://acme-v02.api.letsencrypt.org/acme/order/417612000](https://acme-v02.api.letsencrypt.org/acme/order/417612000)  
[https://acme-v02.api.letsencrypt.org/acme/finalize/64583000](https://acme-v02.api.letsencrypt.org/acme/finalize/64583000)

id number has changed by me.

---

<div class="post-metadata">

**Author:** ![webprofusion](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/webprofusion/32/85310_2.png) [@webprofusion](https://community.letsencrypt.org/u/webprofusion)\
**Post date:** [April 2, 2022, 3:55am UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/9 "2022-04-02T03:55:21Z")

</div>

Yes, if you check the log and look at an order URL the account id is the first number:

`https://acme-v02.api.letsencrypt.org/acme/order/ **<account id>** /<order id>`

So then your full account id url is  
`https://acme-v02.api.letsencrypt.org/acme/acct/<account id>`

---

<div class="post-metadata">

**Author:** ![GodSir](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@GodSir](https://community.letsencrypt.org/u/GodSir)\
**Post date:** [April 2, 2022, 9:00am UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/10 "2022-04-02T09:00:03Z")

</div>

> [@webprofusion](#):
>
> [https://acme-v02.api.letsencrypt.org/acme/acct/](https://acme-v02.api.letsencrypt.org/acme/acct/)

I have submitted my application, how long will this take?

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [April 2, 2022, 9:14am UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/11 "2022-04-02T09:14:06Z")

</div>

Some weeks. 2-6 if I had to guess.

---

<div class="post-metadata">

**Author:** ![GodSir](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@GodSir](https://community.letsencrypt.org/u/GodSir)\
**Post date:** [April 3, 2022, 7:22am UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/12 "2022-04-03T07:22:11Z")

</div>

too long waiting... 🫠

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [April 3, 2022, 7:46am UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/13 "2022-04-03T07:46:45Z")

</div>

If you want it, ask and forget about it. One day, you'll get an email.

---

<div class="post-metadata">

**Author:** ![GodSir](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@GodSir](https://community.letsencrypt.org/u/GodSir)\
**Post date:** [April 3, 2022, 8:05am UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/14 "2022-04-03T08:05:34Z")

</div>

Sounds like winning the lottery.... 😳

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [April 3, 2022, 8:06am UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/15 "2022-04-03T08:06:15Z")

</div>

It **will** happen. You just don't know **when**. 😃

---

<div class="post-metadata">

**Author:** ![GodSir](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@GodSir](https://community.letsencrypt.org/u/GodSir)\
**Post date:** [April 3, 2022, 3:52pm UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/16 "2022-04-03T15:52:25Z")

</div>

Maybe I should go burn incense and pray... 😶‍🌫️

---

<div class="post-metadata">

**Author:** ![GodSir](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@GodSir](https://community.letsencrypt.org/u/GodSir)\
**Post date:** [April 26, 2022, 1:31pm UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/17 "2022-04-26T13:31:51Z")

</div>

i get x2 cert now. but test site show "This server's certificate chain is incomplete. Grade capped to B."

[https://www.ssllabs.com/ssltest/analyze.html?d=m.xiaoyu.net&s=134.195.121.55](https://www.ssllabs.com/ssltest/analyze.html?d=m.xiaoyu.net&s=134.195.121.55)

How i fix it?

---

<div class="post-metadata">

**Author:** ![mcpherrinm](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mcpherrinm/32/59604_2.png) [@mcpherrinm](https://community.letsencrypt.org/u/mcpherrinm)\
**Post date:** [April 26, 2022, 2:42pm UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/19 "2022-04-26T14:42:10Z")

</div>

This is because the X2 (ECDSA) root isn't in the version of the trust stores that SSL Labs has.  
There is a cross-sign from the X1 root to the X2 root, which is what SSL Labs is calling an "extra download".

You have two options:

1. Wait for software to update to include the x2 root and this issue will eventually go away. This is the reason the X2 root is still behind an allow-list, as there may be compatibility issues still.

2. Include the X2 cross-sign in the chain served by your TLS server. You can get a copy of it here: [https://letsencrypt.org/certs/isrg-root-x2-cross-signed.pem](https://letsencrypt.org/certs/isrg-root-x2-cross-signed.pem) -- I'm not sure offhand if the ACME API includes it.

---

<div class="post-metadata">

**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\
**Post date:** [April 26, 2022, 2:44pm UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/20 "2022-04-26T14:44:32Z")

</div>

> [@mcpherrinm](#):
>
> I'm not sure offhand if the ACME API includes it.

It does. It's not only the default, it's the only proposed chain.

---

<div class="post-metadata">

**Author:** ![GodSir](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@GodSir](https://community.letsencrypt.org/u/GodSir)\
**Post date:** [April 26, 2022, 2:50pm UTC](https://community.letsencrypt.org/t/get-isrg-root-x2/174887/21 "2022-04-26T14:50:25Z")

</div>

i have installed isrg-root-x2-cross-signed.der in windows 2022 IIS. but it still not fix it...

[Next page](https://community.letsencrypt.org/t/get-isrg-root-x2/174887.md?page=2)
