# 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:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![cogdog](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cogdog/32/116536_2.png) [@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")

</div>

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:

 ![not-https](https://global.discourse-cdn.com/meta/original/3X/8/3/83ebaec1a5063d3cfe1e69e8cdd244583a2bbd6f.jpeg)

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.

---

_[View the full topic](https://meta.discourse.org/t/an-iframe-in-a-post-reports-not-https/208122)._