2 hours ago · Tech · hide · 0 comments

Here's my setup in a nutshell. I've got a Plex quadlet running on the host network because Plex is finicky about networks. If I run it on a bridge network, Plex The Service thinks my server is "remote" and needs a "relay connection" even if I'm trying to stream media on my LAN. And now that Plex The Service charges a subscription to stream remotely, that's not an option for me. I'm using Caddy as a reverse proxy for the various services on my server. For everything except Plex, that means the quadlets live on a custom bridge network called "proxy". That makes the Caddy config file easy as I can route traffic to containers by name. Plex is the exception since it lives on the host network. For Plex, plex.local:80 routes to host.containers.internal:32400. host.containers.internal is the neutral equivalent to host.docker.internal (which is also supported as of writing this). Unfortunately this setup broke at some point between the end of February and today, when I noticed the issue. I…

No comments yet. Log in to reply on the Fediverse. Comments will appear here.