For context, my test site is behind a reverse proxy running in my homelab because I don’t have infinite IPs. I have it forwarded to port 80 because it works and I’m not interested in breaking things.
However this isn’t a “fix my proxy setup” support post, the one thing I’ve noticed is that no many how times I tell this notice to go away it always comes back:
If you have valid ssl, You can just set force_https to true and this warning will go away. The warning only shows up after rebuilding or when you’re accessing from a new browser (so assuming the dismiss is cookie based). In your case it looks like your reverse proxy is already terminating ssl so you can safely enable force https in discourse.
I have opened a PR which, if merged, would allow you to actually ignore notices from select problem checks, together with another dashboard tab where you can see the status of all your checks and undo the ignore.
Note that this is subject to review and merge by Discourse staff, e.g. @kris.kotlarek.
