Network
Follow a request
Networking is mostly a chain of small handovers. Pick a journey and step through it. No jargon is assumed, and nothing here is a live feed.
Journeys
The published path is Cloudflare Tunnel → Nginx → static files. Each step below explains one hop.
Step 1 of 5
A visitor asks for a page
They type the address. Their browser looks the name up and connects to the address it gets back, which belongs to Cloudflare, not to my house.
Left out on purpose: My home address never appears in this step.
Jellyfin reaches the internet through the same tunnel as the website, so no new router port was opened for it.
Step 1 of 4
A user opens the Jellyfin address
The request goes to Cloudflare, just like a website visit.
Pi-hole and Unbound run on the Raspberry Pi. This is how that arrangement generally works; exact settings are not published.
Step 1 of 4
A device needs an address
Before anything loads, a device turns a name into an address by asking its DNS server, which on my network is the Pi.
Tailscale is the documented private remote-access layer. The published pages don’t list which machines have joined.
Step 1 of 3
I’m away and need a machine
For example, to SSH into the laptop, which is a documented use.
Beszel was chosen over a heavier Grafana and Prometheus stack. It has two parts, a hub and an agent, so the whole picture is short.
Step 1 of 4
A small agent runs on each monitored machine
In July 2026 that meant the Proxmox host, the Raspberry Pi 4 and a Windows machine. The agent measures CPU, memory, temperature and uptime locally.
Not a network request but a journey worth following: how new game data reached the archived desktop app without ever overwriting a user’s saves.
Step 1 of 4
The game’s catalogue changes
New cards, skills and scenarios appear. The app needs them, but users shouldn’t each have to scrape anything.