Disclosure: I work on Zorven, one of the outbound tunnel options mentioned below. Every option here includes its real trade-offs, including when you should skip Zorven and use Tailscale or a plain VPS instead.

You set up Home Assistant at home, open http://homeassistant.local:8123, everything loads on Wi-Fi—then you turn off Wi-Fi on your phone and nothing connects. Adding a port forward for 8123 or 443 in your router doesn't change anything either.

In 2026, the usual culprit on residential fiber, 5G home routers, and standard Starlink plans is CGNAT (Carrier-Grade NAT). Because multiple households share one ISP-level public IPv4 address, unsolicited inbound traffic never reaches your router at all.

Here is how to confirm CGNAT in 60 seconds, choose the right outbound path for your threat model, and configure Home Assistant's configuration.yaml so you don't hit 400: Bad Request once traffic starts flowing.

Step 1: Confirm whether you are behind CGNAT (and whether IPv6 works)

Check the WAN IP shown on your router's status page against your visible public IPv4 address:

curl -4 https://ifconfig.me 

You are behind CGNAT if:

  • Your router's WAN IP is in 100.64.0.0/10 (100.64.x.x through 100.127.x.x), OR
  • Your router's WAN IP does not match what ifconfig.me prints.

Check whether your connection has routable IPv6 as well:

curl -6 https://ifconfig.me 

If your phone network and work Wi-Fi both have IPv6 and your router exposes an IPv6 firewall rule, native IPv6 is the cleanest path—but many mobile/corporate networks still drop IPv6, which brings us to outbound tunnels.

Step 2: Pick the right outbound approach for who needs access

Option A — Only you and household members need access (Best default: Tailscale)

If you don't need public Google Assistant / Alexa / webhook callbacks and just want the Home Assistant Companion app to work away from home:

  1. Install the Tailscale Home Assistant add-on (or run tailscale up on your host).
  2. Install Tailscale on your phone and reach http://<tailscale-node-name>:8123 over WireGuard.
  3. Zero ports exposed to public internet scanners.

When Tailscale isn't enough: Tailscale Funnel lets you expose port 443/8443/10000 publicly without the app, though Funnel bandwidth isn't configurable and its control plane is SaaS-only.

Option B — You need a public HTTPS URL (cloudflared / Cloudflare Tunnel)

For external webhooks (Owntracks, iOS shortcuts, Google Home integration) on a domain managed in Cloudflare DNS:

cloudflared tunnel login cloudflared tunnel create ha-home cloudflared tunnel route dns ha-home ha.yourdomain.com 

Create config.yml:

tunnel: ha-home credentials-file: /root/.cloudflared/<TUNNEL-ID>.json ingress: - hostname: ha.yourdomain.com service: http://127.0.0.1:8123 - service: http_status:404 

Start it with cloudflared tunnel run ha-home. Putting Cloudflare Access in front adds an email-PIN login gate before Home Assistant sees any HTTP traffic.

Trade-off: Cloudflare terminates TLS at its edge, requires your domain DNS on Cloudflare, and the tunnel control plane cannot be self-hosted.

Option C — Full ownership on your own $4–5/mo VPS (WireGuard + Caddy or frp)

Rent a cheap VPS with a real public IPv4 address, keep a WireGuard tunnel open outbound from home (PersistentKeepalive = 25), and let Caddy on the VPS terminate HTTPS and reverse-proxy to Home Assistant over the tunnel IP. Zero vendor lock-in, zero SaaS limits—at the cost of maintaining OS updates, firewall rules, and TLS routing yourself.

Option D — Open-source, self-hostable tunnel with built-in edge auth (Zorven)

If you want cloudflared-style ergonomics without vendor lock-in (either hosted at zorven.app or self-hosted via Docker Compose on your own VPS, AGPL-3.0):

# Install client (Linux / macOS) curl -fsSL https://zorven.app/install.sh | sudo bash # Save token from dashboard and publish port 8123 zorven authtoken zrv_live_... zorven http 8123 

Typical client output:

Forwarding https://myhome--user.zorven.app -> http://localhost:8123 

What fits Home Assistant specifically:

  • You can enable visitor authentication (Basic, Google, or GitHub login) or IP allow-lists at the edge before requests ever reach localhost:8123.
  • Hosted plans throttle rather than hard-cutting connections if a monthly allowance is reached, and self-hosting (docker compose up -d on your own VPS) removes hosted traffic caps completely.

When NOT to use Zorven:

  • Only you and your family need access -> use private Tailscale/WireGuard instead.
  • You need a battle-tested multi-region CDN network right now -> Zorven's hosted relay currently runs in a single region, whereas Cloudflare has global edge POPs.

Step 3: Fix Home Assistant's 400: Bad Request reverse proxy check

Whichever HTTP reverse tunnel you pick (cloudflared, Caddy over WireGuard, or Zorven), Home Assistant rejects forwarded requests by default until you explicitly declare your local proxy IP trusted.

Edit /config/configuration.yaml (or via Studio Code Server add-on):

http: use_x_forwarded_for: true trusted_proxies: - 127.0.0.1 - ::1 # If running Home Assistant inside Docker bridge networking, also add your bridge/host IP:  # - 172.30.33.0/24 

Restart Home Assistant (Developer Tools -> YAML -> Restart). If you still see 400: Bad Request, check Settings -> System -> Logs for a line like:

ERROR (MainThread) [homeassistant.components.http.forwarded] A request from a reverse proxy was received from 172.17.0.1, but your HTTP integration is not set-up for reverse proxies 

Add that exact logged IP to trusted_proxies and restart once more.

Security checklist before sharing the URL publicly

  1. Keep configuration.yaml binding Home Assistant strictly to localhost (server_host: 127.0.0.1 if not running add-ons directly on another container bridge).
  2. Enable 2FA (TOTP) on every Home Assistant user account.
  3. Prefer putting an edge auth layer (Cloudflare Access or Zorven visitor login) in front of Home Assistant if external webhooks aren't hitting /api/webhook/....
  4. Leave /api/webhook/... excluded from interactive browser login only if you rely on external webhook senders.

Repos / docs:

  • Home Assistant HTTP integration: https://www.home-assistant.io/integrations/http/
  • Zorven (AGPL-3.0): https://github.com/tkodcumpeg4/zorven (https://zorven.app)