# Scontro tra OAuth2 e Letsencrypt

**URL:** https://meta.discourse.org/t/oauth2-and-letsencrypt-clash/394536
**Category:** Support
**Tags:** oauth2, letsencrypt
**Created:** [28 Gennaio 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:** 4

<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: [28 Gennaio 2026, 2:37pm UTC](https://meta.discourse.org/t/oauth2-and-letsencrypt-clash/394536/4 "2026-01-28T14:37:27Z")

</div>

> [@Ostap1974](#):
>
> Ho trovato un file `/etc/nginx/conf.d/outlets/before-server/20-redirect-http-to-https.conf` che sembra restituire sempre un 301 a [https://community.site](https://community.site) per qualsiasi richiesta sulla porta 80.

Quel problema è stato risolto lo scorso agosto, [letsencrypt updates: renew location for .well-known, add support for … · discourse/discourse\_docker@ae4887a · GitHub](https://github.com/discourse/discourse_docker/commit/ae4887a4f716b68f53f547f603be3b834a2b0c78)

---

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