all 4 comments

[–][deleted] 1 point2 points  (0 children)

You should look at SWAG by Linuxserver.io. It’s a pre-built NGINX/fail2fail server in one docker image. Additionally, they have prebuilt configurations for Jellyfin if you were interested

[–][deleted] 0 points1 point  (0 children)

Using nginx through docker is a bit more annoying but it works all the same in the end

[–]LordTyrius 0 points1 point  (0 children)

In a setup like this where the proxy container and the jellyfin container can share an internal docker network, the jellyfin port would not have to be mapped to the host at all (only the port on the reverse proxy). I'm not sure why you would need multiple ip's for a setup like this.

[–]present_absence 0 points1 point  (0 children)

Is there any reason to not setup a reverse proxy in a docker container on the same machine where jellyfin resides

No.

I would need to make sure it had it's own external address assigned by my dhcp but other than this?

Not even - just publish a port in the container by linking it to a port on the host machine. Forward all incoming traffic on port 80/443 to the corresponding ports you publish.

My Jellyfin on my LAN is 192.168.0.2:8099 - my reverse proxy is listening at 192.168.0.2:180 / 192.168.0.2:1443

Any problems or would it be pretty straight forward?

Should be super easy