# 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:** [23.Февраль.2015 16:47:05 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:** 7
**Page:** 1

<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: [23.Февраль.2015 16:47:05 UTC](https://meta.discourse.org/t/bug-livestream-mixed-content-warning-causing-onebox-not-to-render/25572/1 "2015-02-23T16:47:05Z")

</div>

For example:  
[http://new.livestream.com/internetsociety/codeacrossnyc2015](http://new.livestream.com/internetsociety/codeacrossnyc2015)

(not working here, because, I guess livestream is not in the whitelist )

And the odd thing is, onebox is rendering in preview, but once you hit New Topic, it doesn’t work.

Using 1.3.0beta1

---

<div class="post-metadata">

### Author: ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [23.Февраль.2015 19:08:08 UTC](https://meta.discourse.org/t/bug-livestream-mixed-content-warning-causing-onebox-not-to-render/25572/2 "2015-02-23T19:08:08Z")

</div>

It looks like livestream doesn’t support HTTPS? When I change that URL to HTTPS it just redirects back. So if you are using HTTPS on a discourse, you will get a mixed content warning.

---

<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: [23.Февраль.2015 19:26:59 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?

---

<div class="post-metadata">

### Author: ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [23.Февраль.2015 20:23:39 UTC](https://meta.discourse.org/t/bug-livestream-mixed-content-warning-causing-onebox-not-to-render/25572/4 "2015-02-23T20:23:39Z")

</div>

I don’t think it’s possible to fix unless livestream adds HTTPS support.

---

<div class="post-metadata">

### Author: ![DeanMarkTaylor](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/deanmarktaylor/32/102462_2.png) [@DeanMarkTaylor](https://meta.discourse.org/u/DeanMarkTaylor)
#### Post date: [23.Февраль.2015 20:38:32 UTC](https://meta.discourse.org/t/bug-livestream-mixed-content-warning-causing-onebox-not-to-render/25572/5 "2015-02-23T20:38:32Z")

</div>

They have support for HTTPS - but their Canonical redirects are messed up.

[http://new.livestream.com/internetsociety/codeacrossnyc2015/embed](http://new.livestream.com/internetsociety/codeacrossnyc2015/embed)

 ![](https://global.discourse-cdn.com/meta/original/3X/6/f/6f339793c2633bbd63cc34c174cf274624a933a3.png)

 ![](https://global.discourse-cdn.com/meta/original/3X/1/6/1622803770fa27cec55ac8bcf3731cad37ffd527.png)

---

<div class="post-metadata">

### Author: ![eviltrout](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eviltrout/32/5275_2.png) [@eviltrout](https://meta.discourse.org/u/eviltrout)
#### Post date: [24.Февраль.2015 16:36:16 UTC](https://meta.discourse.org/t/bug-livestream-mixed-content-warning-causing-onebox-not-to-render/25572/6 "2015-02-24T16:36:16Z")

</div>

I just added support for Livestream via forced HTTPS to onebox in master:

[http://new.livestream.com/wnyw/live](http://new.livestream.com/wnyw/live)

^^^ It looks like the preview image gives a mixed content warning but once the video is rendered it goes away. That should be OK for most people as only the poster will see the warning briefly.

---

<div class="post-metadata">

### Author: ![techAPJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techapj/32/342990_2.png) [@techAPJ](https://meta.discourse.org/u/techAPJ)
#### Post date: [01.Январь.2016 16:07:25 UTC](https://meta.discourse.org/t/bug-livestream-mixed-content-warning-causing-onebox-not-to-render/25572/7 "2016-01-01T16:07:25Z")

</div>