# Want get R13 (ISRG Root X1) with acme.sh or certbot script

**URL:** <https://community.letsencrypt.org/t/want-get-r13-isrg-root-x1-with-acme-sh-or-certbot-script/247835>\
**Category:** Help\
**Created:** [June 3, 2026, 6:05am UTC](https://community.letsencrypt.org/t/want-get-r13-isrg-root-x1-with-acme-sh-or-certbot-script/247835 "2026-06-03T06:05:55Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [June 4, 2026, 12:17pm UTC](https://community.letsencrypt.org/t/want-get-r13-isrg-root-x1-with-acme-sh-or-certbot-script/247835/14 "2026-06-04T12:17:25Z")

</div>

> [@akshay.halemani](#):
>
> I understand that exceptions are generally not made and that the recommended approach is to update devices to support the new certificate chain

I am not sure you do understand the best way forward for you. You should post a new thread asking for assistance on that. Your best path is probably to use a private CA. That would give you complete control of the certs. But, for a public CA you should be trusting roots and NOT PINNING intermediates. Even roots will change over time. These are the first things Let's Encrypt warns about in the Integration Guide: [Integration Guide - Let's Encrypt](https://letsencrypt.org/docs/integration-guide/#plan-for-change)

With that said, staff monitor this forum and they would need to divert efforts for your case.

There was a similar situation last summer where @aarongable, a member of LE staff, said this: [Is there any way to resume R11 in Let's Encrypt - #5 by aarongable](https://community.letsencrypt.org/t/is-there-any-way-to-resume-r11-in-lets-encrypt/240838/5)

A review of another thread by Aaron from 2020 is also instructive: [IOT Devices with X3 certificate embedded - #13 by aarongable](https://community.letsencrypt.org/t/iot-devices-with-x3-certificate-embedded/140801/13)

> [@akshay.halemani](#):
>
> Given the potential impact on a large installed base

The R13 intermediate you pinned to only started use last August. I applaud your ability to obtain a large installed base in such a short period of time. People using such new products are often understanding of the "growing pains". Yes, it can be painful but in the long run can build trust with your customers. I speak from personal experience of running a tech company.

---

_[View the full topic](https://community.letsencrypt.org/t/want-get-r13-isrg-root-x1-with-acme-sh-or-certbot-script/247835)._
