# Hit Let's encrypt renewal limit

**URL:** https://meta.discourse.org/t/hit-lets-encrypt-renewal-limit/156374
**Category:** Self-hosting
**Created:** [June 30, 2020, 4:09pm UTC](https://meta.discourse.org/t/hit-lets-encrypt-renewal-limit/156374 "2020-06-30T16:09:00Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![jomaxro](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jomaxro/32/126216_2.png) [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [July 1, 2020, 9:58am UTC](https://meta.discourse.org/t/hit-lets-encrypt-renewal-limit/156374/7 "2020-07-01T09:58:25Z")

</div>

> [@gpetrov](#):
>
> The whole initial problem was caused by not working Ipv6 support in discourse that prevented the let’s encrypt certificates from renewal. We had a AAAA dns record but discourse didn’t reply on the Ipv6 address and certificates failed to renew.

It’d be great if you could create a new topic to debug this. Discourse fully supports IPv6. Meta works over IPv6, as do all our hosted sites. I’ve run multiple self-hosted sites with IPv6 working too. All have working SSL via Let’s Encrypt.

---

_[View the full topic](https://meta.discourse.org/t/hit-lets-encrypt-renewal-limit/156374)._