Saturday, 31 October 2026
Home-lab design part 5 - The perfect Serviio console
Continuing my [2026 homelab uplift series](https://blog.themillhousegroup.com/search/label/homelab), when I found my RPi 3B was no-longer cutting it with H265 videos, it was a no-brainer to try a [dockerised Serviio](https://hub.docker.com/r/soerentsch/serviio) on my Nuc/Proxmox/Alpine/Docker stack.
Some quick tests showed it to be extremely smooth.
But - for devices on your home network to see the DLNA advertisements from this Serviio instance, you need to do some tricky Docker networking so that your container is running in your network (e.g. for me, 10.240.0.0/16, maybe 192.168.0.0/24 for you, but probably NOT the 172.19.0.0/16 that a Docker container will typically be running in if not specifically configured)
While Arcane does support defining these networks within its GUI, it's got a bit of an impedance mismatch, so I head to the Proxmox console for my Docker VM. The command that worked for me was:
```
# docker network create \
-d macvlan \
--subnet=10.240.0.0/16 \
--gateway=10.240.0.1 \
--ip-range=10.240.1.96/30 \
-o parent=eth0 \
macvlan-on-home-network
```
This [Visual Subnet Calculator](https://www.davidc.net/sites/default/subnets/subnets.html) may prove handy if you're trying to find a safe IP range for your Serviio container to slot into!
This will now get DLNA advertisements out onto your home network, and devices will start showing Serviio(whatever) in their server lists. Note: it's highly likely that the `whatever` part of the server name will be random hex due to Docker, so you might want to edit your `profiles.xml` and replace `Serviio({hostname})` with a fixed string like just `Serviio`.
You'll also be able to access the Serviio console at `http://10.240.1.96:23423/console` or whatever, but that's both insecure and has an ugly and hard-to-remember port number, which we're able to eliminate with Nginx Proxy Manager, so let's get that working.
Sadly, simply adding a straightforward Proxy Host to make `https://serviio.lab.example.com` point to ``http://10.240.1.96:23423` won't work, because, by Docker design, the NGinx Docker container **cannot see into that MacVLAN network**; you'll get a _No Route To Host_ error, which manifests as a 502 in your browser.
#### Containers can't talk to each other
```mermaid
architecture-beta
group lab(affinity:house)[Home Lab]
group docker(affinity:grid)[Docker] in lab
service serviio(affinity:camera)[Serviio] in docker
service firewall(affinity:firewall) in docker
service npm(affinity:loadbalancer)[NPM] in docker
npm:R <-- L:firewall
firewall:R --> L:serviio
align row npm serviio
```
Now you *could* get extremely tricky with your Docker (and Alpine, and Proxmox) networking stack to get around this, and I'm sure it's possible following guides like [this MacVLAN document](https://blog.oddbit.com/post/2018-03-12-using-docker-macvlan-networks/) and maybe asking a friendly chatbot, but I've never really felt comfortable with advanced networking (routing, firewalls, IPtables etc etc) on Linux and would rather throw some existing specialised hardware at it. The right tool for the job I think. So instead, I'm punching through this limitation with my old friends [the Mikrotik hairpin triplets](https://blog.themillhousegroup.com/2025/07/mikrotik-automation.html), aka what a consumer-grade router calls "port forwarding".
### Mikrotik saves the day again
Going from the outside-in, here's how the Nginx Proxy Manager setup looks:
The trick here is that the host `mikrotik` has *nothing at all to do with Docker*, so packets can happily make their way from NPM to the router and then on to _the actual service_. Time for a diagram.
#### After
```mermaid
architecture-beta
group lab(affinity:house)[Home Lab]
group docker(affinity:grid)[Docker] in lab
service serviio(affinity:camera)[Serviio] in docker
service npm(affinity:loadbalancer)[NPM] in docker
service mikrotik(affinity:router)[Mikrotik] in lab
npm:L <--> B:mikrotik
mikrotik:R <--> T:serviio
align row npm serviio
```
##### Filter rules:
See [the aforementioned Mikrotik post](https://blog.themillhousegroup.com/2025/07/mikrotik-automation.html) for the details, but here's how it looks for the Serviio rules.
Allow Serviio packets (destined for port 23423) to cross the routing fabric.
##### NAT Rules:
The "outbound" DST-Nat rule:
Packets (destined for port 23423 of "me") get their destination IP rewritten to that of the Serviio container.
The "hairpin" SRC-Nat rule:
Packets (destined for port 23423 of "me") _also_ get their source IP rewritten to the Mikrotik's IP so that the container will respond to the right place.
Labels:
docker,
docker-compose,
markdown-enabled,
networking,
proxmox,
proxmoxve,
serviio
Subscribe to:
Post Comments (Atom)




No comments:
Post a Comment
Comments welcome - spam is not. Spam will be detected, deleted and the source IP blocked.