# An iframe in a post reports not HTTPs
**URL:** https://meta.discourse.org/t/an-iframe-in-a-post-reports-not-https/208122
**Category:** Support
**Created:** [November 3, 2021, 3:19pm UTC](https://meta.discourse.org/t/an-iframe-in-a-post-reports-not-https/208122 "2021-11-03T15:19:44Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@cogdog](https://meta.discourse.org/u/cogdog)
#### Post date: [November 3, 2021, 3:19pm UTC](https://meta.discourse.org/t/an-iframe-in-a-post-reports-not-https/208122/1 "2021-11-03T15:19:44Z")
Our education community allows users to use iframes to insert [H5P](https://h5p.org/) (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:
[https://connect.oeglobal.org/t/contribute-your-voice-to-oeg-voices-opening-segment/3213/19](https://connect.oeglobal.org/t/contribute-your-voice-to-oeg-voices-opening-segment/3213/19)
The same embed works as expected in a WordPress site [Is This Thing On? – The H5P Kitchen](https://kitchen.opened.ca/microphone/)
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.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [November 3, 2021, 3:40pm UTC](https://meta.discourse.org/t/an-iframe-in-a-post-reports-not-https/208122/2 "2021-11-03T15:40:07Z")
Have you upgraded from the command line recently? Is `force_https` enabled?
---
### Author:  [@cogdog](https://meta.discourse.org/u/cogdog)
#### Post date: [November 3, 2021, 4:59pm UTC](https://meta.discourse.org/t/an-iframe-in-a-post-reports-not-https/208122/3 "2021-11-03T16:59:36Z")
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?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [November 3, 2021, 5:21pm UTC](https://meta.discourse.org/t/an-iframe-in-a-post-reports-not-https/208122/4 "2021-11-03T17:21:34Z")
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.
---
### Author:  [@cogdog](https://meta.discourse.org/u/cogdog)
#### Post date: [November 3, 2021, 6:51pm UTC](https://meta.discourse.org/t/an-iframe-in-a-post-reports-not-https/208122/5 "2021-11-03T18:51:37Z")
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.
---
### Author:  [@cogdog](https://meta.discourse.org/u/cogdog)
#### Post date: [November 4, 2021, 6:59pm UTC](https://meta.discourse.org/t/an-iframe-in-a-post-reports-not-https/208122/6 "2021-11-04T18:59:26Z")
The issue is to grant access to the microphone via an iframe allow= parameter is stripped from iframe tags in discourse, [as reported elsewhere](https://meta.discourse.org/t/iframe-attributes-not-working/127383/8).