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: [not-https] All of our discourse content is served as HTTPs, and all urls in the embed are HTT…

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

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.

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…

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

게시물의 iframe이 HTTPs가 아니라고 보고됨

제품 지원

cogdog (Alan Levine) 11월 4, 2021, 6:59오후 6

문제는 마이크 접근을 허용하기 위한 iframe의 allow= 속성이 discourse의 iframe 태그에서 제거된다는 것입니다. 다른 곳에서 보고된 바와 같이.

글		댓글	조회수
Replacement for whitelist-iframe Product Support	1	1959	1월 30, 2018
How to run the discourse in Iframe? Product Support	1	431	4월 17, 2023
Restrict embedded video to HTTPS Product Support	1	503	1월 3, 2021
Add WhiteListIframe embed of everycircuit.com Product Support	9	2522	9월 16, 2019
Discourse not shown in iframe Product Support unsupported-install	30	8971	4월 26, 2021

게시물의 iframe이 HTTPs가 아니라고 보고됨

Related topics