<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Zorven Blog]]></title><description><![CDATA[Zorven Blog]]></description><link>https://zorven.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sat, 21 Nov 2026 15:23:26 GMT</lastBuildDate><atom:link href="https://zorven.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Exposing Home Assistant behind CGNAT without port forwarding (2026)]]></title><description><![CDATA[Step-by-step guide to checking whether your ISP or Starlink uses CGNAT, comparing Tailscale, Cloudflare Tunnel, a WireGuard VPS, and self-hosted Zorven…]]></description><link>https://zorven.hashnode.dev/exposing-home-assistant-behind-cgnat-without-port-forwarding-2026</link><guid isPermaLink="true">https://zorven.hashnode.dev/exposing-home-assistant-behind-cgnat-without-port-forwarding-2026</guid><category><![CDATA[Home Assistant]]></category><category><![CDATA[self-hosted]]></category><category><![CDATA[networking]]></category><category><![CDATA[Homelab]]></category><dc:creator><![CDATA[Zorven App]]></dc:creator><pubDate>Tue, 17 Nov 2026 06:35:03 GMT</pubDate><content:encoded><![CDATA[<p><em>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.</em></p>
<p>You set up Home Assistant at home, open <code>http://homeassistant.local:8123</code>, everything loads on Wi-Fi—then you turn off Wi-Fi on your phone and nothing connects. Adding a port forward for <code>8123</code> or <code>443</code> in your router doesn't change anything either.</p>
<p>In 2026, the usual culprit on residential fiber, 5G home routers, and standard Starlink plans is <strong>CGNAT (Carrier-Grade NAT)</strong>. Because multiple households share one ISP-level public IPv4 address, unsolicited inbound traffic never reaches your router at all.</p>
<p>Here is how to confirm CGNAT in 60 seconds, choose the right outbound path for your threat model, and configure Home Assistant's <code>configuration.yaml</code> so you don't hit <code>400: Bad Request</code> once traffic starts flowing.</p>
<hr />
<h2>Step 1: Confirm whether you are behind CGNAT (and whether IPv6 works)</h2>
<p>Check the WAN IP shown on your router's status page against your visible public IPv4 address:</p>
<pre><code class="language-bash">curl -4 https://ifconfig.me
</code></pre>
<p>You are behind CGNAT if:</p>
<ul>
<li>Your router's WAN IP is in <code>100.64.0.0/10</code> (<code>100.64.x.x</code> through <code>100.127.x.x</code>), OR</li>
<li>Your router's WAN IP does not match what <code>ifconfig.me</code> prints.</li>
</ul>
<p>Check whether your connection has routable IPv6 as well:</p>
<pre><code class="language-bash">curl -6 https://ifconfig.me
</code></pre>
<p>If your phone network and work Wi-Fi <em>both</em> 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.</p>
<hr />
<h2>Step 2: Pick the right outbound approach for who needs access</h2>
<h3>Option A — Only you and household members need access (Best default: Tailscale)</h3>
<p>If you don't need public Google Assistant / Alexa / webhook callbacks and just want the Home Assistant Companion app to work away from home:</p>
<ol>
<li>Install the Tailscale Home Assistant add-on (or run <code>tailscale up</code> on your host).</li>
<li>Install Tailscale on your phone and reach <code>http://&lt;tailscale-node-name&gt;:8123</code> over WireGuard.</li>
<li>Zero ports exposed to public internet scanners.</li>
</ol>
<p><strong>When Tailscale isn't enough:</strong> Tailscale Funnel lets you expose port <code>443</code>/<code>8443</code>/<code>10000</code> publicly without the app, though Funnel bandwidth isn't configurable and its control plane is SaaS-only.</p>
<h3>Option B — You need a public HTTPS URL (<code>cloudflared</code> / Cloudflare Tunnel)</h3>
<p>For external webhooks (Owntracks, iOS shortcuts, Google Home integration) on a domain managed in Cloudflare DNS:</p>
<pre><code class="language-bash">cloudflared tunnel login
cloudflared tunnel create ha-home
cloudflared tunnel route dns ha-home ha.yourdomain.com
</code></pre>
<p>Create <code>config.yml</code>:</p>
<pre><code class="language-yaml">tunnel: ha-home
credentials-file: /root/.cloudflared/&lt;TUNNEL-ID&gt;.json
ingress:
  - hostname: ha.yourdomain.com
    service: http://127.0.0.1:8123
  - service: http_status:404
</code></pre>
<p>Start it with <code>cloudflared tunnel run ha-home</code>. Putting Cloudflare Access in front adds an email-PIN login gate before Home Assistant sees any HTTP traffic.</p>
<p><strong>Trade-off:</strong> Cloudflare terminates TLS at its edge, requires your domain DNS on Cloudflare, and the tunnel control plane cannot be self-hosted.</p>
<h3>Option C — Full ownership on your own $4–5/mo VPS (WireGuard + Caddy or <code>frp</code>)</h3>
<p>Rent a cheap VPS with a real public IPv4 address, keep a WireGuard tunnel open outbound from home (<code>PersistentKeepalive = 25</code>), and let <strong>Caddy</strong> 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.</p>
<h3>Option D — Open-source, self-hostable tunnel with built-in edge auth (<code>Zorven</code>)</h3>
<p>If you want <code>cloudflared</code>-style ergonomics without vendor lock-in (either hosted at <code>zorven.app</code> or self-hosted via Docker Compose on your own VPS, AGPL-3.0):</p>
<pre><code class="language-bash"># 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
</code></pre>
<p>Typical client output:</p>
<pre><code class="language-text">Forwarding  https://myhome--user.zorven.app  -&gt;  http://localhost:8123
</code></pre>
<p>What fits Home Assistant specifically:</p>
<ul>
<li>You can enable visitor authentication (Basic, Google, or GitHub login) or IP allow-lists at the edge before requests ever reach <code>localhost:8123</code>.</li>
<li>Hosted plans throttle rather than hard-cutting connections if a monthly allowance is reached, and self-hosting (<code>docker compose up -d</code> on your own VPS) removes hosted traffic caps completely.</li>
</ul>
<p><strong>When NOT to use Zorven:</strong></p>
<ul>
<li>Only you and your family need access -&gt; use private Tailscale/WireGuard instead.</li>
<li>You need a battle-tested multi-region CDN network right now -&gt; Zorven's hosted relay currently runs in a single region, whereas Cloudflare has global edge POPs.</li>
</ul>
<hr />
<h2>Step 3: Fix Home Assistant's <code>400: Bad Request</code> reverse proxy check</h2>
<p>Whichever HTTP reverse tunnel you pick (<code>cloudflared</code>, Caddy over WireGuard, or Zorven), Home Assistant rejects forwarded requests by default until you explicitly declare your local proxy IP trusted.</p>
<p>Edit <code>/config/configuration.yaml</code> (or via Studio Code Server add-on):</p>
<pre><code class="language-yaml">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
</code></pre>
<p>Restart Home Assistant (<strong>Developer Tools -&gt; YAML -&gt; Restart</strong>). If you still see <code>400: Bad Request</code>, check <strong>Settings -&gt; System -&gt; Logs</strong> for a line like:</p>
<pre><code class="language-text">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
</code></pre>
<p>Add that exact logged IP to <code>trusted_proxies</code> and restart once more.</p>
<hr />
<h2>Security checklist before sharing the URL publicly</h2>
<ol>
<li>Keep <code>configuration.yaml</code> binding Home Assistant strictly to localhost (<code>server_host: 127.0.0.1</code> if not running add-ons directly on another container bridge).</li>
<li>Enable <strong>2FA (TOTP)</strong> on every Home Assistant user account.</li>
<li>Prefer putting an edge auth layer (Cloudflare Access or Zorven visitor login) in front of Home Assistant if external webhooks aren't hitting <code>/api/webhook/...</code>.</li>
<li>Leave <code>/api/webhook/...</code> excluded from interactive browser login only if you rely on external webhook senders.</li>
</ol>
<p><em>Repos / docs:</em></p>
<ul>
<li>Home Assistant HTTP integration: <code>https://www.home-assistant.io/integrations/http/</code></li>
<li>Zorven (<code>AGPL-3.0</code>): <code>https://github.com/tkodcumpeg4/zorven</code> (<code>https://zorven.app</code>)</li>
</ul>
]]></content:encoded></item><item><title><![CDATA[ngrok vs Cloudflare Tunnel vs Tailscale Funnel vs Zorven: an honest comparison (2026)]]></title><description><![CDATA[Comparing outbound tunneling tools for local webhooks, CGNAT homelabs, private networks, and raw TCP/UDP — including where ngrok, cloudflared, and…]]></description><link>https://zorven.hashnode.dev/ngrok-vs-cloudflare-tunnel-vs-tailscale-funnel-vs-zorven-an-honest-comparison-2026</link><guid isPermaLink="true">https://zorven.hashnode.dev/ngrok-vs-cloudflare-tunnel-vs-tailscale-funnel-vs-zorven-an-honest-comparison-2026</guid><category><![CDATA[devtools]]></category><category><![CDATA[self-hosted]]></category><category><![CDATA[networking]]></category><category><![CDATA[open source]]></category><dc:creator><![CDATA[Zorven App]]></dc:creator><pubDate>Tue, 17 Nov 2026 06:24:06 GMT</pubDate><content:encoded><![CDATA[<p><em>Disclosure: I work on Zorven. I kept this comparison conservative: each competitor column reflects documented strengths, and the bottom section lists where you should pick one of the other three instead.</em></p>
<p>All four tools solve the same surface problem: you want traffic from the internet (or another network) to reach a service running on your laptop or home server without opening inbound router ports. Under the hood, they optimize for very different jobs.</p>
<h2>Quick comparison</h2>
<table>
<thead>
<tr>
<th>Dimension</th>
<th>ngrok</th>
<th>Cloudflare Tunnel (<code>cloudflared</code>)</th>
<th>Tailscale / Tailscale Funnel</th>
<th>Zorven</th>
</tr>
</thead>
<tbody><tr>
<td><strong>Open-source server</strong></td>
<td>No (client agent historically open, server proprietary)</td>
<td>No (<code>cloudflared</code> daemon open, edge proprietary)</td>
<td>Partial (client OSS, coordination server proprietary; community <code>headscale</code> exists separately)</td>
<td><strong>Yes (AGPL-3.0)</strong></td>
</tr>
<tr>
<td><strong>Self-hostable control plane</strong></td>
<td>No</td>
<td>No</td>
<td>No (official); requires <code>headscale</code> for self-hosted control plane</td>
<td><strong>Yes (Go server + Docker Compose)</strong></td>
</tr>
<tr>
<td><strong>One-command HTTP tunnel</strong></td>
<td><code>ngrok http 3000</code></td>
<td><code>cloudflared tunnel --url http://localhost:3000</code></td>
<td><code>tailscale funnel 3000</code></td>
<td><code>zorven http 3000</code></td>
</tr>
<tr>
<td><strong>Raw TCP / UDP tunnels</strong></td>
<td>TCP yes (paid/verified card for some endpoints)</td>
<td>TCP via Cloudflare Access/Spectrum setups; not aimed at arbitrary UDP</td>
<td>Private mesh handles TCP/UDP; Funnel HTTPS-only on fixed ports (<code>443</code>, <code>8443</code>, <code>10000</code>)</td>
<td><strong>TCP on all plans; advanced UDP (game servers) on Pro and up</strong></td>
</tr>
<tr>
<td><strong>Private device-to-device WireGuard mesh</strong></td>
<td>No</td>
<td>Private WARP/Zero Trust connectors</td>
<td><strong>Yes (best-in-class tailnet)</strong></td>
<td><strong>Yes (Zorven Net, <code>zorven share</code> / <code>zorven net up</code>)</strong></td>
</tr>
<tr>
<td><strong>Built-in webhook replay / inspector</strong></td>
<td><strong>Yes (<code>localhost:4040</code>, very mature)</strong></td>
<td>No built-in webhook replay UI</td>
<td>No</td>
<td><strong>Yes (live request log + replay &amp; diff)</strong></td>
</tr>
<tr>
<td><strong>Free tier behavior</strong></td>
<td>Usage/request limits, dev domain, browser interstitial warning unless skipped</td>
<td>Generous free tunnel (requires Cloudflare-managed domain for stable hostnames; ToS restricts heavy video proxy)</td>
<td>Generous personal tailnet; Funnel non-configurable bandwidth limits</td>
<td>Free plan (2 tunnels, 5 GB/mo) <strong>throttles on overage instead of hard cutoffs</strong> (Free drops to 1 Mbps, Hobby 5 Mbps)</td>
</tr>
<tr>
<td><strong>Global edge POP maturity</strong></td>
<td>Multi-region global POPs</td>
<td><strong>Largest global anycast network</strong></td>
<td>Global DERP relay network</td>
<td>Single-region hosted relay right now (multi-region only if you deploy multiple self-hosted servers)</td>
</tr>
</tbody></table>
<hr />
<h2>Deep dive by use case</h2>
<h3>1. When ngrok is still the fastest choice</h3>
<ul>
<li>You just want to inspect a local Stripe/Shopify webhook with a mature local inspector UI at <code>http://127.0.0.1:4040</code> and don't need self-hosting.</li>
<li>You rely on low-latency global edge POPs across multiple continents and don't hit the monthly free bandwidth / browser interstitial friction.</li>
</ul>
<h3>2. When Cloudflare Tunnel (<code>cloudflared</code>) wins</h3>
<ul>
<li>Your domain DNS is already on Cloudflare, you want Cloudflare Access (Zero Trust SSO/email OTP) in front of self-hosted web apps, and you want massive global anycast DDoS absorption for $0.</li>
<li><strong>Watch out for:</strong> Cloudflare ends up terminating TLS on their edge, your control plane isn't self-hosted, and heavy non-HTML traffic (e.g., streaming Plex/Jellyfin media libraries) can run afoul of their proxy Terms of Service.</li>
</ul>
<h3>3. When Tailscale (and Funnel) wins</h3>
<ul>
<li>If access is <strong>only for you, your devices, or your team</strong>—not random unauthenticated browser visitors—a private tailnet beats any public URL hands down. MagicDNS, mobile clients, ACLs, and direct UDP hole punching are rock-solid.</li>
<li>Tailscale Funnel is great for quick light sharing on ports <code>443</code>/<code>8443</code>/<code>10000</code>, though it wasn't built as an arbitrary TCP/UDP ingress or a webhook replay debugger.</li>
</ul>
<h3>4. Where Zorven fits (<code>https://zorven.app</code>)</h3>
<p>Zorven tries to combine the pieces developers usually duct-tape together from ngrok + Tailscale + a Caddy reverse proxy—without locking the control plane inside a SaaS:</p>
<pre><code class="language-bash"># Quick temporary URL that cleans itself up after 30m:
zorven ephemeral 3000 --ttl 30m

# Clean scripting output for CI / wrappers:
zorven http 3000 --print-url

# Share a local Postgres port privately with one teammate (end-to-end encrypted):
zorven share 5432 --to colleague@company.com --name db
</code></pre>
<p>Where it stands out today:</p>
<ul>
<li><strong>AGPL-3.0 open source and self-hostable:</strong> Deploy the whole server (<code>server/</code> Go binary + Nuxt dashboard + Postgres via <code>deploy/docker-compose.yml</code>) on a $5 VPS under your own domain.</li>
<li><strong>Flat per-plan hosted pricing ($0 Free / $5 Hobby / $12 Pro / $29 Team):</strong> Not per-user or per-seat—useful if an agency, studio, or field installer manages multiple customer sites.</li>
<li><strong>Extras in one binary:</strong> Request inspector with replay, visitor login gates (Basic / Google / GitHub), UDP/TCP ports + SNI passthrough, browser terminal/screen share (<code>--enable-terminal</code> / <code>--enable-screen</code>, off by default), and built-in MCP server (<code>zorven mcp</code>).</li>
</ul>
<hr />
<h2>When NOT to pick Zorven</h2>
<ol>
<li><strong>You need a battle-tested multi-region edge today.</strong> Cloudflare and ngrok have years of global multi-POP reliability; Zorven is young (~v0.x, 8 GitHub stars) and its hosted service runs in one region right now.</li>
<li><strong>You strictly need a private mesh for personal devices.</strong> Tailscale's native OS apps and onboarding polish are much more mature if you never expose public URLs.</li>
<li><strong>You don't want AGPL-3.0 for proprietary redistribution.</strong> Zorven is AGPL-3.0 open source; check license compatibility before embedding the server into commercial proprietary appliances.</li>
</ol>
<hr />
<p><em>Links:</em></p>
<ul>
<li>Zorven repository: <code>https://github.com/tkodcumpeg4/zorven</code></li>
<li>Hosted site: <code>https://zorven.app</code></li>
</ul>
]]></content:encoded></item><item><title><![CDATA[How to access Plex, Jellyfin or Home Assistant behind CGNAT or Starlink (2026): 5 options compared]]></title><description><![CDATA[Disclosure: I work on Zorven, one of the tools compared below. I tried to be fair, including saying when you should not use it. You set up Plex, Jellyfin…]]></description><link>https://zorven.hashnode.dev/how-to-access-plex-jellyfin-or-home-assistant-behind-cgnat-or-starlink-2026-5-options-compared</link><guid isPermaLink="true">https://zorven.hashnode.dev/how-to-access-plex-jellyfin-or-home-assistant-behind-cgnat-or-starlink-2026-5-options-compared</guid><category><![CDATA[#selfhosted]]></category><category><![CDATA[Homelab]]></category><category><![CDATA[networking]]></category><category><![CDATA[Plex]]></category><dc:creator><![CDATA[Zorven App]]></dc:creator><pubDate>Sat, 14 Nov 2026 10:35:36 GMT</pubDate><content:encoded><![CDATA[<p><em>Disclosure: I work on Zorven, one of the tools compared below. I tried to be fair, including saying when you should not use it.</em></p>
<p>You set up Plex, Jellyfin or Home Assistant at home. It works on the couch. Then you try to reach it from your phone on mobile data and nothing happens, and port forwarding in your router does nothing.</p>
<p>The usual cause is <strong>CGNAT</strong> (carrier-grade NAT). Your ISP, and Starlink on standard residential plans, puts many customers behind one shared public IPv4 address. Your router never gets a public IPv4 address of its own, so inbound connections have nowhere to land. Quick check: compare the WAN IP shown in your router's admin page with what a "what is my IP" site reports. If they differ, or the WAN IP is in <code>100.64.0.0/10</code> (or a private range such as <code>10.x</code>), you are behind CGNAT.</p>
<p>There are several ways around it. Below are five options (the first one has two variants) with real commands, honest trade-offs and a comparison table.</p>
<p>Default ports used in the examples: Plex <code>32400</code>, Jellyfin <code>8096</code>, Home Assistant <code>8123</code>.</p>
<h2>Option 1: Get a routable address (ISP public IPv4, or IPv6)</h2>
<h3>1a. Ask your ISP for a public IPv4 or static IP</h3>
<p>The cleanest fix is to not be behind CGNAT at all. Many ISPs will take you out of CGNAT on request, sometimes free, sometimes for a monthly fee. Starlink has offered a paid public IPv4 option in some regions; check what your plan and region allow today.</p>
<p>Then you forward the port as usual and, because home IPs change, add dynamic DNS.</p>
<p><strong>Pros:</strong> no extra software, full bandwidth, lowest latency.
<strong>Cons:</strong> not every ISP offers it; may cost money; you are now directly exposed to the internet, so you need TLS (a reverse proxy such as Caddy), updates, and strong auth. Home Assistant and Jellyfin should never be exposed on plain HTTP.</p>
<h3>1b. Use IPv6</h3>
<p>Many CGNAT connections still have native IPv6, and IPv6 addresses are usually globally routable, so no NAT is involved. Check:</p>
<pre><code class="language-bash">curl -6 https://ifconfig.me
</code></pre>
<p>If that returns an address, you have IPv6. Add an <code>AAAA</code> record pointing at your server, and open the port in your <strong>router's IPv6 firewall</strong> (it blocks inbound by default). Not all routers, and not all Starlink setups, make that easy.</p>
<p><strong>Pros:</strong> free, no middleman, full speed.
<strong>Cons:</strong> the <em>client</em> also needs IPv6, and many mobile networks and workplace or hotel networks still do not. Your IPv6 prefix can change. You still need TLS and auth. Treat this as a bonus path, rarely the only one.</p>
<h2>Option 2: Tailscale (including Funnel)</h2>
<p>Tailscale builds a WireGuard-based private network (a "tailnet") between your devices, and it traverses CGNAT fine because connections start outbound, falling back to relays when a direct path is impossible.</p>
<pre><code class="language-bash">curl -fsSL https://tailscale.com/install.sh | sh
sudo tailscale up
</code></pre>
<p>Install Tailscale on your phone and laptop too, and reach the server at its tailnet name or <code>100.x</code> address, for example <code>http://homeserver:8096</code>. Nothing is exposed publicly. For Plex, Jellyfin and Home Assistant used by you and your family, this is often the best answer.</p>
<p><strong>Funnel</strong> lets you publish a service to the public internet through Tailscale:</p>
<pre><code class="language-bash">sudo tailscale funnel 8096
</code></pre>
<p>Funnel must be enabled in your tailnet policy first, and it only listens on a few ports (443, 8443 and 10000 at the time of writing). Tailscale documents bandwidth limits on Funnel that are not configurable, so it is better for light use than for sharing a media library with friends. Check their current docs.</p>
<p><strong>Pros:</strong> very easy, secure by default, great for personal use, free personal tier.
<strong>Cons:</strong> every viewer needs the Tailscale app (unless you use Funnel); Funnel is limited in ports and bandwidth; the control plane is a hosted service.</p>
<h2>Option 3: Cloudflare Tunnel</h2>
<p><code>cloudflared</code> makes an outbound connection to Cloudflare, which then serves your hostname. You need a domain on Cloudflare.</p>
<pre><code class="language-bash">cloudflared tunnel login
cloudflared tunnel create home
cloudflared tunnel route dns home ha.example.com
</code></pre>
<p>Then a <code>config.yml</code>:</p>
<pre><code class="language-yaml">tunnel: home
credentials-file: /home/you/.cloudflared/&lt;TUNNEL-ID&gt;.json
ingress:
  - hostname: ha.example.com
    service: http://localhost:8123
  - service: http_status:404
</code></pre>
<pre><code class="language-bash">cloudflared tunnel run home
</code></pre>
<p><strong>Important caveat for Plex and Jellyfin:</strong> Cloudflare's terms have long restricted serving disproportionate amounts of non-HTML content, notably video, through its proxy on the free and self-serve plans. People have reported accounts being warned or throttled for streaming media over tunnels. Read the current Terms of Service yourself before putting a media server behind it. For Home Assistant, which is small JSON and websockets, it is generally a fine fit.</p>
<p><strong>Pros:</strong> free, mature, DDoS protection and optional Cloudflare Access login in front.
<strong>Cons:</strong> the ToS risk above for video; Cloudflare terminates TLS and sees your traffic; you must use a domain on their DNS; hosted service you cannot self-host.</p>
<h2>Option 4: VPS + WireGuard or frp</h2>
<p>Rent a small VPS with a public IP (a few dollars a month), and connect your home machine to it outbound. Anything arriving at the VPS gets carried home.</p>
<p>With <strong>frp</strong>, on the VPS (<code>frps.toml</code>):</p>
<pre><code class="language-toml">bindPort = 7000
auth.token = "change-me"
</code></pre>
<p>At home (<code>frpc.toml</code>):</p>
<pre><code class="language-toml">serverAddr = "YOUR.VPS.IP"
serverPort = 7000
auth.token = "change-me"

[[proxies]]
name = "jellyfin"
type = "tcp"
localIP = "127.0.0.1"
localPort = 8096
remotePort = 8096
</code></pre>
<p>Run <code>./frps -c frps.toml</code> on the VPS and <code>./frpc -c frpc.toml</code> at home. Put Caddy or Nginx on the VPS if you want HTTPS on a real domain.</p>
<p>With <strong>WireGuard</strong>, you make the home machine a peer of the VPS with <code>PersistentKeepalive = 25</code> (so the outbound hole stays open), then forward or reverse-proxy from the VPS to the home peer's tunnel IP.</p>
<p><strong>Pros:</strong> you own everything; no ToS issues; bandwidth limited only by your VPS plan; works for any protocol.
<strong>Cons:</strong> you maintain a server (patches, firewall, certs); home upload and VPS bandwidth both matter; more setup than anything else here.</p>
<h2>Option 5: Zorven</h2>
<p>Zorven is an open-source (AGPL-3.0), self-hostable tunnel service. The client opens one outbound connection, so it works behind CGNAT without port forwarding. Clients exist for Windows, macOS and Linux.</p>
<pre><code class="language-bash"># Linux / macOS
curl -fsSL https://zorven.app/install.sh | sudo bash
# Windows (PowerShell)
irm https://zorven.app/install.ps1 | iex

zorven authtoken zrv_live_...   # token from the dashboard
zorven http 8123                # Home Assistant
</code></pre>
<p>The client prints a public HTTPS address that forwards to <code>localhost:8123</code>. Swap the port for <code>8096</code> (Jellyfin) or <code>32400</code> (Plex). You can add visitor login (Basic, Google, GitHub), IP allow-lists and rate limits in front of the app, and use your own domain.</p>
<p>The free plan has 2 tunnels and <strong>5 GB of monthly traffic</strong>; Pro is $12/month with 100 GB. You can also run the whole server yourself on a VPS, which the README describes as unlimited for self-hosting. If you are happy to run a VPS anyway, that overlaps with Option 4, but with the TLS, hostnames and auth layer included.</p>
<h2>Comparison</h2>
<table>
<thead>
<tr>
<th></th>
<th>ISP public IP</th>
<th>IPv6</th>
<th>Tailscale / Funnel</th>
<th>Cloudflare Tunnel</th>
<th>VPS + WireGuard/frp</th>
<th>Zorven</th>
</tr>
</thead>
<tbody><tr>
<td>Works behind CGNAT</td>
<td>Removes it</td>
<td>If you have IPv6</td>
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Cost</td>
<td>Free to paid</td>
<td>Free</td>
<td>Free personal tier</td>
<td>Free + domain</td>
<td>VPS fee</td>
<td>Free / $12 Pro / self-host</td>
</tr>
<tr>
<td>Public HTTPS URL</td>
<td>DIY</td>
<td>DIY</td>
<td>Funnel only</td>
<td>Yes</td>
<td>DIY (Caddy)</td>
<td>Yes</td>
</tr>
<tr>
<td>Viewers need an app</td>
<td>No</td>
<td>No</td>
<td>Yes (not for Funnel)</td>
<td>No</td>
<td>No</td>
<td>No</td>
</tr>
<tr>
<td>Video streaming friendly</td>
<td>Yes</td>
<td>Yes</td>
<td>Private yes; Funnel limited</td>
<td>Check ToS</td>
<td>Yes</td>
<td>Quota-limited on hosted plans</td>
</tr>
<tr>
<td>Self-hostable</td>
<td>n/a</td>
<td>n/a</td>
<td>No (hosted control plane)</td>
<td>No</td>
<td>Yes</td>
<td>Yes</td>
</tr>
<tr>
<td>Setup effort</td>
<td>Low</td>
<td>Medium</td>
<td>Low</td>
<td>Medium</td>
<td>High</td>
<td>Low</td>
</tr>
</tbody></table>
<h2>When NOT to use Zorven</h2>
<ul>
<li><strong>You mostly stream big media files.</strong> On the hosted plans, traffic is capped (5 GB free, 100 GB on Pro). A single 1080p stream at 8 Mbps uses roughly 3.6 GB per hour, so the free plan covers well under two hours. For a media library shared with others, use Tailscale (private), a VPS you control, or self-host Zorven on a VPS with enough bandwidth.</li>
<li><strong>Only you and your family need access.</strong> Tailscale without Funnel is simpler and keeps everything off the public internet.</li>
<li><strong>You already have a public IPv4 or working IPv6.</strong> Port forwarding plus a reverse proxy is fewer moving parts.</li>
<li><strong>You need a vendor with a long track record.</strong> Zorven is young. Cloudflare and Tailscale are far more battle-tested.</li>
<li><strong>You need guaranteed streaming behavior.</strong> I have not benchmarked Plex or Jellyfin transcoding over Zorven, so test it with your own library before relying on it.</li>
</ul>
<h2>Security note for all options</h2>
<p>Anything public will be scanned. Use HTTPS, keep Plex, Jellyfin and Home Assistant updated, use strong unique passwords and 2FA where offered, and consider putting an authentication layer in front. For Home Assistant behind any reverse proxy or tunnel, you also need to trust the proxy in <code>configuration.yaml</code>:</p>
<pre><code class="language-yaml">http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 127.0.0.1
</code></pre>
<p>Adjust <code>trusted_proxies</code> to the address your tunnel client connects from.</p>
<h2>What I would do</h2>
<ul>
<li>Family-only access: Tailscale.</li>
<li>Home Assistant public URL for webhooks or voice assistants: Cloudflare Tunnel or Zorven.</li>
<li>Sharing a media library: a VPS you control, or self-hosted Zorven on one.</li>
<li>Public IPv4 available cheaply from your ISP: take it, and add a reverse proxy.</li>
</ul>
<p>Zorven: <a href="https://zorven.app">https://zorven.app</a>, source: <a href="https://github.com/tkodcumpeg4/zorven">https://github.com/tkodcumpeg4/zorven</a></p>
<p><em>Plans, limits and terms change. Double-check each vendor's current documentation before you commit.</em></p>
]]></content:encoded></item></channel></rss>