# Insecure content from markdown-it-bundle when using https

**URL:** https://meta.discourse.org/t/insecure-content-from-markdown-it-bundle-when-using-https/66559
**Category:** Support
**Created:** [July 20, 2017, 9:32pm UTC](https://meta.discourse.org/t/insecure-content-from-markdown-it-bundle-when-using-https/66559 "2017-07-20T21:32:20Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![mr8](https://avatars.discourse-cdn.com/v4/letter/m/f9ae1b/32.png) [@mr8](https://meta.discourse.org/u/mr8)
#### Post date: [July 20, 2017, 9:32pm UTC](https://meta.discourse.org/t/insecure-content-from-markdown-it-bundle-when-using-https/66559/1 "2017-07-20T21:32:20Z")

</div>

Recently updated my copy of discourse and noticed this weird little bug in the console that also prevents the preview window from loading.

```
[blocked] The page at https://domain.com/t/topic/4512/484 was not allowed to run insecure content from http://domain.com/assets/markdown-it-bundle-d1f9395746d57602322789f6d8cdbfcb43f414005bb7a41e18cb6fdbeede9796.js.

```

Only get this error when accessing the site via https. Accessing the site via regular http eliminates the problem and the preview loads as usual.

Did I miss a recent change somewhere in the setting that I need to adjust so that that particular asset gets loaded over https when connecting via https? All other assets seem to be loading correctly.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [July 20, 2017, 9:34pm UTC](https://meta.discourse.org/t/insecure-content-from-markdown-it-bundle-when-using-https/66559/2 "2017-07-20T21:34:32Z")

</div>

If you turn the site setting `force_https` ON, it should work, can you try that?

---

<div class="post-metadata">

### Author: ![mr8](https://avatars.discourse-cdn.com/v4/letter/m/f9ae1b/32.png) [@mr8](https://meta.discourse.org/u/mr8)
#### Post date: [July 20, 2017, 9:36pm UTC](https://meta.discourse.org/t/insecure-content-from-markdown-it-bundle-when-using-https/66559/3 "2017-07-20T21:36:23Z")

</div>

Already have that enabled.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [July 20, 2017, 9:37pm UTC](https://meta.discourse.org/t/insecure-content-from-markdown-it-bundle-when-using-https/66559/4 "2017-07-20T21:37:08Z")

</div>

> [@mr8](#):
>
> Only get this error when accessing the site via https. Accessing the site via regular http eliminates the problem and the preview loads as usual.

> [@mr8](#):
>
> Already have that enabled.

If you have that enable how can you access the site via HTTP? 🤔

---

<div class="post-metadata">

### Author: ![mr8](https://avatars.discourse-cdn.com/v4/letter/m/f9ae1b/32.png) [@mr8](https://meta.discourse.org/u/mr8)
#### Post date: [July 20, 2017, 9:38pm UTC](https://meta.discourse.org/t/insecure-content-from-markdown-it-bundle-when-using-https/66559/5 "2017-07-20T21:38:04Z")

</div>

Adding:

```
proxy_set_header X-Forwarded-Proto https;

```

to my outer nginx fixed this by letting discourse know that I needed the `https://` assets instead of the `https://` ones.

---

<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: [July 20, 2017, 11:07pm UTC](https://meta.discourse.org/t/insecure-content-from-markdown-it-bundle-when-using-https/66559/6 "2017-07-20T23:07:55Z")

</div>


