# Mixed Content: The page at '\<URL\>' was loaded over HTTPS error

**URL:** https://meta.discourse.org/t/mixed-content-the-page-at-url-was-loaded-over-https-error/216404
**Category:** Support
**Created:** [January 29, 2022, 9:39am UTC](https://meta.discourse.org/t/mixed-content-the-page-at-url-was-loaded-over-https-error/216404 "2022-01-29T09:39:04Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![poyrazdursuncan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/poyrazdursuncan/32/204976_2.png) [@poyrazdursuncan](https://meta.discourse.org/u/poyrazdursuncan)
#### Post date: [January 31, 2022, 6:16am UTC](https://meta.discourse.org/t/mixed-content-the-page-at-url-was-loaded-over-https-error/216404/7 "2022-01-31T06:16:09Z")

</div>

_Solved._

> [@Install Discourse on a residential internet with Cloudflare Tunnel](https://meta.discourse.org/t/discourse-on-a-residential-internet-with-cloudflare-tunnel/211297):
>
> Since [Discourse now has support for running on a Raspberry Pi](https://blog.discourse.org/2021/12/2021-12-07-discourse-on-a-raspberry-pi/), running a small instance in your home lab will become a common use case. However, many residential ISPs block incoming traffic to the ports 80/443 that Discourse need. For our demo site at [https://discourse-on-a-pi.falco.dev/](https://discourse-on-a-pi.falco.dev/) we used [Cloudflare Tunnel](https://blog.cloudflare.com/tunnel-for-everyone/) to work around this, and you can do it too! Setup your tunnel First, follow the following guide: The only change you need is changing the URL from url: http://localhost:8000 to url…

---

_[View the full topic](https://meta.discourse.org/t/mixed-content-the-page-at-url-was-loaded-over-https-error/216404)._
