Clearing advice doesn't actually clear it

[darkpixlz (Pyx)]

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:

Is the “dismiss” button’s job to not.. dismiss the message?

[itsbhanusharma (Bhanu Sharma)]

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.

[Moin]

@darkpixlz

Is the “dismiss” button’s job to not.. dismiss the message?

Not really

@ted

However, if the underlying problem isn’t fixed, it will come back when you reload the page.

This is known behaviour. The current feature is to get rid of “stuck” or one-off notices. We’re working on extending this functionality to let you “snooze” these notifications for a set time frame, so they won’t show up immediately again.