In a Support topic titled Flashing warning when adding Font Awesome 5 to Discourse, foodaginnovators reported seeing a flashing warning about force_https not being enabled — despite having SSL — even as a basic user, which shouldn’t happen. The warning appeared on posts, not just in admin, and persisted after enabling force_https, refreshing, and logging out/in. A gif showed the issue. vinothkannans noted the warning icon isn’t core Discourse, suggesting a plugin or theme; pfaffman confirmed no plugins were installed and asked about safe mode. foodaginnovators traced the issue to manually adding Font Awesome 5’s script in the header — a workaround for missing icons — which triggered the warning, though it didn’t appear immediately. They reverted to Discourse’s built-in icons. codinghorror noted Discourse will eventually upgrade from FA4 to FA5, asking why FA5 was needed urgently. foodaginnovators clarified they only wanted an unsupported external link icon and are fine with the default. Alankrit_Choudh shared a link to FA5.1.0 icons, including one themed for Discourse. jomaxro clarified FA5 was added in Discourse 2.2.0.beta5 and is now stable, making manual FA5 inclusion unnecessary. The issue was resolved by removing the manual script and using Discourse’s native FA5 support.
On self-hosted discourse instance, v2.0.0.beta2 +40, when logged in as basic user with no admin / moderation capability I am seeing the flashing warning with no explanation. The reason for it is recently installed https and need to enable a setting, but this warning shouldn’t be shown to regular users I would think.
Why I’m getting the warning:
Your website is using SSL. But force_https is not yet enabled in your site settings.
What you mean by “flashing warning” and where it was displayed? It is designed to display only inside the admin dashboard. Can you share you a screenshot?
I actually can’t get rid of it now even though I checked enable force https. I see it on posts, not just in admin. Closed tab, hard refresh, logged in and out. This screenshot is from my admin account. I also see it on basic account as well in posts.
Got it. I put font awesome script into header <script defer src="https://use.fontawesome.com/releases/v5.0.6/js/all.js"></script>. I guess that was causing it, although when I initially inserted it two days ago I didn’t get the warning. Must be a more efficient way to add font awesome icons that are not available in discourse, that is topic for another post though. For now have used one that is supported out of the box by discourse.
We will eventually upgrade from Font Awesome 4 (which we already use heavily for the glyphs in Discourse) to Font Awesome 5. What’s so urgent that you needed 5 right now, just out of curiosity?
Awesome! Honestly, I was trying to use an external link alt icon that wasn’t supported. But I’m totally fine with the regular external link icon and now using that which works. So nothing urgent.