# HTTPS tramite Proxy; Discourse tenta ancora di ottenere file tramite HTTP

**URL:** https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749
**Category:** Self-hosting
**Created:** [3 Aprile 2020, 7:40pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749 "2020-04-03T19:40:58Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![CRUGG](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crugg/32/161184_2.png) [@CRUGG](https://meta.discourse.org/u/CRUGG)
#### Post date: [3 Aprile 2020, 7:40pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/1 "2020-04-03T19:40:58Z")

</div>

Ciao! Ho appena provato a configurare il mio forum Discourse. Quando ho cliccato sul link nell’email, ho visto un pulsante ma non sono riuscito a premere. Ho notato diversi errori, che sembrano essere causati dal tentativo di caricare file tramite HTTP. Questo potrebbe essere dovuto al fatto che non sto utilizzando HTTPS tramite Discourse, ma piuttosto tramite il mio server web apache2 usando un ProxyPass. Come posso far sì che richieda i file tramite HTTPS senza utilizzare l’HTTPS di Discourse? (O indicami un modo per utilizzare i miei file .crt e .key già esistenti in modo semplice, che funzioni altrettanto bene 😉)

 ![image](https://global.discourse-cdn.com/meta/original/3X/0/c/0c30300ccda25517d786259a7534aa01cdc7d54d.png)

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [3 Aprile 2020, 7:48pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/2 "2020-04-03T19:48:23Z")

</div>

Hai abilitato l’uso forzato di HTTPS in Discourse?

---

<div class="post-metadata">

### Author: ![CRUGG](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crugg/32/161184_2.png) [@CRUGG](https://meta.discourse.org/u/CRUGG)
#### Post date: [3 Aprile 2020, 7:50pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/3 "2020-04-03T19:50:32Z")

</div>

Come potrei farlo? (senza utilizzare LetsEncrypt o SSL tramite Discourse)  
Dovrei semplicemente decommentare `templates/web.ssl.template.yml` e lasciare `templates/web.letsencrypt.ssl.template.yml` commentato? (Scusa per la domanda, ma la ricostruzione richiede così tanto tempo che preferisco essere sicuro)

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [3 Aprile 2020, 8:03pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/4 "2020-04-03T20:03:20Z")

</div>

Basta andare nelle impostazioni e attivare la casella che dice ‘force https’.

Per chiarezza, assicurati al 100% che il tuo reverse proxy possa gestire SSL per Discourse prima di abilitare quell’impostazione.

⚠ Discourse non funziona bene con Apache2… Se possibile, passa a Nginx.

---

<div class="post-metadata">

### Author: ![CRUGG](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crugg/32/161184_2.png) [@CRUGG](https://meta.discourse.org/u/CRUGG)
#### Post date: [3 Aprile 2020, 8:03pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/5 "2020-04-03T20:03:50Z")

</div>

Aspetta, quali impostazioni? Dove diavolo dovrei trovare una casella di controllo?

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [3 Aprile 2020, 8:04pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/6 "2020-04-03T20:04:49Z")

</div>

`community.example.net/admin` è il percorso in cui troverai il pannello di amministrazione di Discourse.

---

<div class="post-metadata">

### Author: ![CRUGG](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crugg/32/161184_2.png) [@CRUGG](https://meta.discourse.org/u/CRUGG)
#### Post date: [3 Aprile 2020, 8:05pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/7 "2020-04-03T20:05:37Z")

</div>

Ma per farlo ho bisogno di un account sul mio forum, che non posso creare senza risolvere il problema HTTPS

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [3 Aprile 2020, 8:11pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/12 "2020-04-03T20:11:21Z")

</div>

Puoi abilitare l’SSL forzato tramite la console:

```plaintext
./launcher enter app
rails c
SiteSetting.force_https = true
exit
exit

```

---

<div class="post-metadata">

### Author: ![CRUGG](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crugg/32/161184_2.png) [@CRUGG](https://meta.discourse.org/u/CRUGG)
#### Post date: [3 Aprile 2020, 8:12pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/13 "2020-04-03T20:12:35Z")

</div>

Devo ricostruire o fare qualcosa dopo?  
Modifica: l’ho ricostruito. Ricevo ancora lo stesso errore che alcuni file vengono ancora caricati tramite HTTP

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [3 Aprile 2020, 8:32pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/14 "2020-04-03T20:32:01Z")

</div>

`force_https` è stato rimosso dall’interfaccia di amministrazione in quanto ha creato più confusione che altro.

Poiché Discourse ora installa HTTPS di default, è solo in casi come questo che è necessario abilitarlo manualmente.

---

<div class="post-metadata">

### Author: ![CRUGG](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crugg/32/161184_2.png) [@CRUGG](https://meta.discourse.org/u/CRUGG)
#### Post date: [3 Aprile 2020, 8:33pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/15 "2020-04-03T20:33:46Z")

</div>

Non era abilitato di default per me. Stavo avendo problemi a utilizzare lo script di installazione, quindi ho modificato il file app.yml. È questo il motivo?

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [3 Aprile 2020, 8:34pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/16 "2020-04-03T20:34:54Z")

</div>

Stai utilizzando HTTP dietro il proxy disabilitando il template per HTTPS?

---

<div class="post-metadata">

### Author: ![CRUGG](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crugg/32/161184_2.png) [@CRUGG](https://meta.discourse.org/u/CRUGG)
#### Post date: [3 Aprile 2020, 8:39pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/17 "2020-04-03T20:39:33Z")

</div>

I due template HTTPS sono stati disabilitati di default per me.  
Discourse è in esecuzione sulle due porte predefinite su Server 2.  
Sto quindi utilizzando un ProxyPass in un VHost apache2 (in esecuzione su Server 1) dove SSL è configurato.  
Ho appena notato che posso abilitare HTTPS direttamente tramite Discourse e, dato che Discourse è in esecuzione sulle porte predefinite, posso semplicemente inserire community.website.tld nell’indirizzo IP di Server 2.  
Come procedo per abilitare SSL? Devo decommentare i due template e poi inserire l’email di LetsEncrypt? Inoltre, come creo un account su LetsEncrypt? Non riesco a trovare alcun pulsante “Registrati” sul loro sito web.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [3 Aprile 2020, 8:50pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/18 "2020-04-03T20:50:31Z")

</div>

Esattamente così: abilita il template per HTTPS e Let’s Encrypt, assicurati che la porta 443 sia esposta e specifica un indirizzo email prima di ricostruire.

Ci sono pochissimi motivi validi per mettere Discourse dietro un proxy. Se ha un server dedicato e un FQDN, sarà molto più semplice gestirlo con quanto sopra.

---

<div class="post-metadata">

### Author: ![CRUGG](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crugg/32/161184_2.png) [@CRUGG](https://meta.discourse.org/u/CRUGG)
#### Post date: [3 Aprile 2020, 8:52pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/19 "2020-04-03T20:52:02Z")

</div>

Ma quale indirizzo e-mail devo specificare lì? Dice che serve un account Let’s Encrypt, quindi devo crearne uno? Dove?

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [3 Aprile 2020, 8:52pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/20 "2020-04-03T20:52:30Z")

</div>

Basta un indirizzo email per ricevere le notifiche. Non è necessario registrarlo in anticipo.

---

<div class="post-metadata">

### Author: ![CRUGG](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crugg/32/161184_2.png) [@CRUGG](https://meta.discourse.org/u/CRUGG)
#### Post date: [3 Aprile 2020, 9:07pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/21 "2020-04-03T21:07:54Z")

</div>

Ho appena abilitato SSL e tutto il resto, ma ora ricevo un errore Cloudflare 502.

 ![image](https://global.discourse-cdn.com/meta/original/3X/8/5/85bb08e566186aa86954b1e62cd15f31375c028b.png)

---

<div class="post-metadata">

### Author: ![riking](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/riking/32/170938_2.png) [@riking](https://meta.discourse.org/u/riking)
#### Post date: [3 Aprile 2020, 9:19pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/22 "2020-04-03T21:19:12Z")

</div>

Assicurati che il proxy imposti correttamente l’intestazione X-Forwarded-Proto su `https`, il che dovrebbe risolvere il rilevamento di https.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [3 Aprile 2020, 9:27pm UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/23 "2020-04-03T21:27:50Z")

</div>

Disattiva Cloudflare per ora. A meno che tu non sia frequentemente attaccato, causa più danni che benefici.

Se la nuvola arancione è abilitata, Discourse non può ottenere il certificato da Let’s Encrypt.

---

<div class="post-metadata">

### Author: ![CRUGG](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/crugg/32/161184_2.png) [@CRUGG](https://meta.discourse.org/u/CRUGG)
#### Post date: [4 Aprile 2020, 7:53am UTC](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749/24 "2020-04-04T07:53:44Z")

</div>

Fatto. HTTPS funziona ora, sta caricando tutto tramite HTTPS, MA:  
Non riesco ancora a premere il pulsante nella Pagina di Verifica dell’Account.

 ![image](https://global.discourse-cdn.com/meta/original/3X/3/5/3525c731357579689b21a54b800d480c1fd32871.png)  
C’è un errore e alcuni avvisi anche nella Console:  
 ![image](https://global.discourse-cdn.com/meta/original/3X/8/6/86f5b1a15698c3aa7110c63945a8cc8d5ab42a73.png)

[Pagina seguente](https://meta.discourse.org/t/https-through-proxy-discourse-still-trying-to-get-files-using-http/146749.md?page=2)
