# Port 443 not accessible using hostname and Port 80 also fails

**URL:** https://meta.discourse.org/t/port-443-not-accessible-using-hostname-and-port-80-also-fails/395326
**Category:** Self-hosting
**Created:** [February 5, 2026, 9:36pm UTC](https://meta.discourse.org/t/port-443-not-accessible-using-hostname-and-port-80-also-fails/395326 "2026-02-05T21:36:57Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![NateDhaliwal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/natedhaliwal/32/313494_2.png) [@NateDhaliwal](https://meta.discourse.org/u/NateDhaliwal)
#### Post date: [February 5, 2026, 10:54pm UTC](https://meta.discourse.org/t/port-443-not-accessible-using-hostname-and-port-80-also-fails/395326/2 "2026-02-05T22:54:56Z")

</div>

Hmm… are you following:

> [@Install Discourse on a residential internet with Cloudflare Tunnel](https://meta.discourse.org/t/install-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/port-443-not-accessible-using-hostname-and-port-80-also-fails/395326)._
