I have recently switched to having Discourse listen on a Unix socket and proxying through an nginx server on the underlying Linux system. Works great.
However, Discourse builds all of its internal links with
http, so it’s mixed content warnings all over the place.
Is there a simple way to force this issue in
DISCOURSE_PROTOCOL would be great but I don’t think it exists.
I did try configuring nginx to pass a protocol header, but this doesn’t appear to make any difference:
proxy_set_header X-Forwarded-Proto "https";
Any thoughts? Thanks.