We set Nginx has a front-end proxy for discourse docker (with sock Add an offline page to display when Discourse is rebuilding or starting up). Then we set HTTPS Lets’ Encrypt outside the container (acme.sh) and everything works fine except onebox for internal link. Onebox is not able to show the preview of internal links. They are as external links HTTPS link [image] Same link in HTTP: [image] Is there a way to fix this issue?

Is force_ssl checked on site settings? Obligatory, please share a link to the forum in a support topic.

[image] Falco: Is force_ssl checked on site settings? Do you meen force_https on the admin panel? I can’t find force_ssl on site settings. [image] AduForum Il network P2P ad alte prestazioni

Trash: Do you meen force_https on the admin panel? Yes, and looks like you don’t. Also, when checking this, if you reverse proxy is badly configured, it’s gonna break your site.

[image] Falco: Also, when checking this, if you reverse proxy is badly configured, it’s gonna break your site. Just made a backup, we will try to check the “force_https” setting. Do you confirm that even if discourse runs through sock, and so the “ssl template” is commented out, everything should work fine? Our reverse proxy is configured to redirect all http traffic to https.

Trash: Do you confirm that even if discourse runs through sock, and so the “ssl template” is commented out, everything should work fine? I’m not really a fan of running reverse proxy in self-hosted environments, unless you are very comfortable with your reverse proxy of choice. That said, if you have all the correct headers set, it will work.

[image] Falco: That said, if you have all the correct headers set, it will work. Which headers would that be? Here’s what I have: location / { proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock; proxy_set_header Host $http_host; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; client_max_body_size 20M; error_page 502 =502 /errorpages/offline.html; proxy_intercept_errors on; error_page 500 503 504 /errorpages/50x.html; }

Issue Onebox in HTTPS

Product Support Self-hosting

dax (Daniela) February 24, 2017, 4:24pm 7

It works perfectly now.
Thanks for the support @Falco.

Topic		Replies	Views
Discourse always generates links to itself with http: rather than https: Product Support	3	735	December 10, 2018
Discourse not aware of SSL termination (mixed content) Self-hosting	7	2102	August 8, 2019
HTTPS through Proxy; Discourse still trying to get files using HTTP Self-hosting	21	1536	April 4, 2020
Reverse Proxy Into Discourse Self-hosting	12	820	October 16, 2024
Front nginx https reverse proxy to discourse http Self-hosting	2	1685	January 8, 2019

Issue Onebox in HTTPS

Related topics