An iframe in a post reports not HTTPs

Our education community allows users to use iframes to insert H5P (HTML5) content which works great as an allowed iframe URL.

But one content type that embeds an audio recorder is reporting this error:

All of our discourse content is served as HTTPs, and all urls in the embed are HTTPs.

This is the place where the error is reported in our discourse:

The same embed works as expected in a WordPress site Is This Thing On? – The H5P PB Kitchen

I realize this may be an issue with the way the source content tests the connection, but am trying to isolate what is different when iframe embedded in discourse.

Have you upgraded from the command line recently? Is force_https enabled?

1 Like

There’s been a command line upgrade in the last 3 weeks. I am finding references to enabling force_https but not how to do this. As not a full on sys admin type but someone with all the keys, can you 'splain it to me?

If you search the admin settings for “force” and don’t see force_https, then it’s set already.

FWIW, I don’t see any http errors on the page you link.

1 Like

Okay thanks, it’s not there.

The developers of the software indicate its probably not an HTTPS issue after all (they acknowledge a poorly worded error message) and more likely an issue of the iframe not granting the feature policy to request access to the microphone (adding allow=“microphone *” did not help.

This is hardly critical I am more curious than anything.

The issue is to grant access to the microphone via an iframe allow= parameter is stripped from iframe tags in discourse, as reported elsewhere.

1 Like