I’m running Discourse in multisite with Caddy, following the very simple setup in examples/discourse at master · caddyserver/examples · GitHub. I’m getting Mixed content errors and warnings in the browser console for site assets like the logos and favicons.
This is for a staging server, showcasing Discourse themes. I’m not planing to run any of this in production as I don’t understand much about server admin. But it would be nice if I could solve the mixed content issue for the staging instances.
Thank you, @timelordx. Yes, it’s not a Caddy issue as such. I’m posting here because it could still be a general issue when using Caddy as reverse proxy for Discourse? In that case it would be helpful not only for me, but also for updating some of the knowledge topics here and on the Discourse community.
That’s a 7-year-old configuration example from a repo that’s been archived for 5 years now.
I’d recommend searching for DISCOURSE_FORCE_HTTPS and “force https” on the Discourse forum - you’ll find more up-to-date info there. Keep in mind, the Caddy documentation can’t possibly cover every web application out there.
Yes, but it’s also a popular topic that got responses until recently on the Discourse community, including references to that 7-yr old configuration example:
So I think it’s quite helpful to keep it up-to-date. Will post an update there and here for reference later.