# How to embed WebM

**URL:** <https://meta.discourse.org/t/how-to-embed-webm/152681>\
**Category:** Support\
**Created:** [May 25, 2020, 6:59pm UTC](https://meta.discourse.org/t/how-to-embed-webm/152681 "2020-05-25T18:59:03Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![miles](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/miles/32/181708_2.png) [@miles](https://meta.discourse.org/u/miles)\
**Post date:** [May 25, 2020, 6:59pm UTC](https://meta.discourse.org/t/how-to-embed-webm/152681/1 "2020-05-25T18:59:03Z")

</div>

I need some help troubleshooting why embedded WebM works on some systems, but not others.

Does this embedded webM clip work for you without opening the link in a new page? What OS and browser are you using?

[https://s1.webmshare.com/jvY0A.webm](https://s1.webmshare.com/jvY0A.webm)

I’m embedding by just pasting the raw url in the message body:

```plaintext
s1.webmshare.com/jvY0A.webm

```

Clickable link: [s1.webmshare.com/jvY0A.webm](http://s1.webmshare.com/jvY0A.webm)

Here are my observations:

| OS | Browser | Result |
| --- | --- | --- |
| Ubuntu 20.04 | Firefox 76 | Fail |
| Ubuntu 20.04 | Chrome 81 | Fail |
| OSX 10.13.6 | Chrome 81 | Fail |
| Andorid 7 | DuckDuckGo | Works |

I believe this used to work on Ubuntu 19.10, but I’m not going to downgrade to double-check.

Here’s what shows-up for me in Firefox:

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

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [March 7, 2021, 8:29am UTC](https://meta.discourse.org/t/how-to-embed-webm/152681/2 "2021-03-07T08:29:18Z")

</div>

I don’t know why the answer would be any different than this:

> **[WebM video format | Can I use... Support tables for HTML5, CSS3, etc](https://caniuse.com/webm)**
>
> "Can I use" provides up-to-date browser support tables for support of front-end web technologies on desktop and mobile web browsers.

---

<div class="post-metadata">

**Author:** ![miles](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/miles/32/181708_2.png) [@miles](https://meta.discourse.org/u/miles)\
**Post date:** [March 7, 2021, 6:38pm UTC](https://meta.discourse.org/t/how-to-embed-webm/152681/3 "2021-03-07T18:38:51Z")

</div>

Is that embedded WebM clip working for you?

I checked again and I’m still getting the “No video with supported format and MIME type found” error in Firefox 86 and Chrome 88 for Ubuntu 20.04. Seems like it should be working according to CanIUse.

---

<div class="post-metadata">

**Author:** ![miles](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/miles/32/181708_2.png) [@miles](https://meta.discourse.org/u/miles)\
**Post date:** [March 7, 2021, 6:52pm UTC](https://meta.discourse.org/t/how-to-embed-webm/152681/4 "2021-03-07T18:52:33Z")

</div>

Also interesting that with the chrome dev console open, the original version works after a refresh:

Chrome first load:

> Mixed Content: The page at ‘[How to embed WebM](https://meta.discourse.org/t/how-to-embed-webm/152681)’ was loaded over HTTPS, but requested an insecure element ‘[http://s1.webmshare.com/jvY0A.webm](http://s1.webmshare.com/jvY0A.webm)’. This request was automatically upgraded to HTTPS, For more information see [Chromium Blog: No More Mixed Messages About HTTPS](https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html)

> Failed to load resource: the server responded with a status of 404 () [webmshare. your free webm hosting and sharing tool](http://s1.webmshare.com/jvY0A.webm:1)

Chrome refresh (surprising that it works now - I guess security settings are relaxed with dev tools open):

> Mixed Content: The page at ‘[How to embed WebM](https://meta.discourse.org/t/how-to-embed-webm/152681)’ was loaded over HTTPS, but requested an insecure element ‘[http://s1.webmshare.com/jvY0A.webm](http://s1.webmshare.com/jvY0A.webm)’. This request was automatically upgraded to HTTPS, For more information see [Chromium Blog: No More Mixed Messages About HTTPS](https://blog.chromium.org/2019/10/no-more-mixed-messages-about-https.html)

The errors are slightly different in Firefox and it continues to fail to load after refresh with dev console open. This consistent behavior seems more reasonable:

> Loading mixed (insecure) display content “[webmshare. your free webm hosting and sharing tool](http://s1.webmshare.com/jvY0A.webm%E2%80%9D) on a secure page

> Failed to load ‘[webmshare. your free webm hosting and sharing tool](http://s1.webmshare.com/jvY0A.webm%E2%80%99). A ServiceWorker passed a promise to FetchEvent.respondWith() that rejected with ‘Error: no-response :: [{“url”:“[http://s1.webmshare.com/jvY0A.webm](http://s1.webmshare.com/jvY0A.webm)”}]’.

> All candidate resources failed to load. Media load paused.

* * *

Seems like a `http` vs `https` issue. With the original link (no prefix), it appears to default to `http://`. Here’s another version that explicitly includes the secure `https://` prefix, but that’s not working either.

```plaintext
https://s1.webmshare.com/jvY0A.webm

```

[https://s1.webmshare.com/jvY0A.webm](https://s1.webmshare.com/jvY0A.webm)

Appears to be an issue with the webmshare host where their https connection is not actually secure.

 ![webmshare-https](https://global.discourse-cdn.com/meta/original/3X/6/7/6716b8d6d7b4007f25d7af5ad8f6d99e4cc06434.png)

A bit annoying that Chrome, Firefox and DDG all handle this issue differently.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [March 7, 2021, 7:25pm UTC](https://meta.discourse.org/t/how-to-embed-webm/152681/5 "2021-03-07T19:25:32Z")

</div>

> [@miles](#):
>
> Appears to be an issue with the webmshare host where their https connection is not actually secure.

Yes, this is not our problem, this is a problem with the specific target site.

---

<div class="post-metadata">

**Author:** ![miles](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/miles/32/181708_2.png) [@miles](https://meta.discourse.org/u/miles)\
**Post date:** [March 7, 2021, 7:26pm UTC](https://meta.discourse.org/t/how-to-embed-webm/152681/6 "2021-03-07T19:26:41Z")

</div>

Turns out it’s most straightforward to just drag and drop .webm files directly into the forum, rather than relying on an external host.

Drag and drop (uploading directly to the discourse instance) generates:

```plaintext
![fontawesome2|video](upload://aI4h9yYRFK9BBCBLED4WcBr6Y1f.webm)

```

And is working fine.

---

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [March 7, 2021, 7:31pm UTC](https://meta.discourse.org/t/how-to-embed-webm/152681/7 "2021-03-07T19:31:41Z")

</div>


