I'm new to Docker and Docker Compose and trying to set up HTTPS access to my Jellyfin server and possibly other services. My Jellyfin is running in a Docker container using Docker Compose, and I also have another container set up with Nginx. I can use Caddy instead if that's easier. I've got a domain hosted through Namecheap for my podcast. I understand that I can point a subdomain to the Nginx container which links to the Jellyfin container using an A record update. However, I'm facing a problem: the Jellyfin container is currently in host mode, which prevents me from adding it to a Docker Network alongside Nginx in Portainer. Is it okay to remove the network mode from the Jellyfin YAML file? How will that affect my currently running Jellyfin server? I'm also not well-versed in how to set up DDNS, but I guess that's a different issue to tackle later.
3 Answers
Using a Docker network for both Jellyfin and Nginx is the way to go! This way, everything runs smoothly on the same port without conflicting. Just ensure that if you have hardware requirements like GPU transcoding, Jellyfin still has access to those resources. Also, you can simplify your DNS management with a wildcard CNAME record for easy subdomain creation.
Generally, avoid host mode unless there's a strong need for it. For Jellyfin, only port mapping is necessary—no network declarations required.
You shouldn't run your Jellyfin container in host mode. Instead, map the ports to your Docker host. The default port for Jellyfin is `8096` (TCP). This way, you can connect it without network mode issues.
Thanks for confirming that! A friend helped me set up the Jellyfin container initially, so I’m still learning the ropes.
Thanks a ton for this info! It's a big help!