# Bug: Livestream mixed content warning causing Onebox not to render

**URL:** <https://meta.discourse.org/t/bug-livestream-mixed-content-warning-causing-onebox-not-to-render/25572>\
**Category:** Bug\
**Created:** [February 23, 2015, 4:47pm UTC](https://meta.discourse.org/t/bug-livestream-mixed-content-warning-causing-onebox-not-to-render/25572 "2015-02-23T16:47:05Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jqnatividad](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jqnatividad/32/115589_2.png) [@jqnatividad](https://meta.discourse.org/u/jqnatividad)\
**Post date:** [February 23, 2015, 7:26pm UTC](https://meta.discourse.org/t/bug-livestream-mixed-content-warning-causing-onebox-not-to-render/25572/3 "2015-02-23T19:26:59Z")

</div>

Yes. That’s exactly what I’m getting since we have HTTPS on.

Any suggested workarounds? Or does this require some extended handling in onebox?

---

_[View the full topic](https://meta.discourse.org/t/bug-livestream-mixed-content-warning-causing-onebox-not-to-render/25572)._