Self-host Jellyfin behind CGNAT with Docker (tested over http only)
Jellyfin is a media server you run yourself. If your internet provider shares one address between many customers (CGNAT), or your router will not forward ports, you cannot watch your library away from home. This page runs Jellyfin in Docker Compose and reaches it from the internet through a TunnelNet address.
Use https before you sign in from outside for real
We tested over plain http on a test machine. Over http, your password crosses the internet unencrypted. Put a reverse proxy with a certificate in front first. The Caddy front door in A public IP for a Docker host behind CGNAT is the pattern, but we have not tested https with Jellyfin.
Tested on
Date: 18 November 2026 · Host: Debian 12, Docker Engine 29.10.0 and Docker Compose v5.8.0, a test virtual machine with 2 CPUs and 2 GB of memory, behind a NAT router with no port forwarding. This is not carrier CGNAT, but inbound behaves the same. · Image: jellyfin/jellyfin:10.10 (Jellyfin 10.10.7) · Media: a 20-second test-pattern video we generated ourselves (no copyrighted media) · On the real service: the normal TunnelNet installer, on an internal test account · The visitor: a test machine in Atlanta.
We drove the first-time setup wizard through Jellyfin's own setup interface instead of clicking through the browser, making the same choices the wizard shows.
Not tested: transcoding (we streamed the original file, "direct play", so as not to load the test box), https, the TV and phone apps, hardware acceleration, carrier CGNAT itself, several viewers at once, and speed. The address 203.0.113.47 is a documentation example.
Before you start
You need a Docker host with TunnelNet installed, so it has its own public address and nothing is open yet. The install is shown in Expose a Docker container without port forwarding.
1. Folders and compose file
$ sudo mkdir -p "/srv/jellyfin/media/Movies/Test Pattern (2026)" && cd /srv/jellyfin
This is the compose.yaml we ran:
services:
jellyfin:
image: jellyfin/jellyfin:10.10
restart: unless-stopped
ports:
- "8096:8096"
volumes:
- config:/config
- cache:/cache
- ./media:/media:ro
volumes:
config:
cache:
The media folder is mounted read-only (:ro), so Jellyfin cannot change your files.
2. Start it
$ sudo docker compose up -d
Container jellyfin-jellyfin-1 Started
$ curl -s http://127.0.0.1:8096/health
Healthy
Undo: sudo docker compose stop.
3. First-time setup
In a browser open http://<host>:8096. These are the choices we made:
- language: en-US;
- an admin user with a strong password;
- Allow remote connections: on;
- automatic port mapping (UPnP): off, because TunnelNet does the reaching-in and there is nothing to map;
- a library called "Movies", type Movies, folder
/media/Movies.
The library scan found Test Pattern (2026).
4. Open it to the internet
$ sudo tnet ports allow tcp 8096 --note=jellyfin
Allowed tcp 8096
From the outside machine:
03:19:15 visitor -> 203.0.113.47:8096/health: Healthy (32 s after allow)
web page /web/: http 200
sign in: ok
play the movie (direct): http 200, 6869183 bytes in 0.74 s
wrong password: http 401
That is one small file and one sample, so it is not a speed figure.
Undo:
$ sudo tnet ports deny 8096
Denied port 8096
It stopped answering 63 seconds later.
Good to know
- In the Jellyfin apps, the server address is
http://<your address>:8096, or your https name once you have one. - Remote viewers use your monthly allowance of 1 TB. As arithmetic, not something we measured: a two-hour film at 8 Mbit/s is about 7 GB.
- Transcoding is the heavy part on a small machine. We did not test it.
Limits
- 1 TB a month is included, then 10 Mbit/s until the 1st of the month (an extra 1 TB costs $15).
- Jellyfin sees viewers as coming from TunnelNet, not from their own address.