# OAuth2 and Letsencrypt clash

**URL:** https://meta.discourse.org/t/oauth2-and-letsencrypt-clash/394536
**Category:** Support
**Tags:** oauth2, letsencrypt
**Created:** [January 28, 2026, 1:07pm UTC](https://meta.discourse.org/t/oauth2-and-letsencrypt-clash/394536 "2026-01-28T13:07:01Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [January 28, 2026, 3:52pm UTC](https://meta.discourse.org/t/oauth2-and-letsencrypt-clash/394536/6 "2026-01-28T15:52:26Z")

</div>

Ah, I see there was more to it, you can read about that [here to the end of that topic](https://meta.discourse.org/t/discourse-failure-to-renew-certificate/385148/10) and then you will see there was [another](https://github.com/discourse/discourse_docker/commit/ebead81303078da7905e9656e2829b2dcf89ffe6) fix on December 22. So that explains why you encountered it.

---

_[View the full topic](https://meta.discourse.org/t/oauth2-and-letsencrypt-clash/394536)._