Hello everyone, I have another question regarding reverse-proxying again, specifically for the linuxserver.io jellyfin image.
On the dockerhub page for this image there are 4 ports listed which should be exposed:
Additionally there is also an environment variable JELLYFIN_PublishedServerUrl
which is for "Setting the autodiscovery response domain or IP address". I currently have that set to my subdomain https://jellyfin.mydomain.com
though I am not sure if that is correct.
I already have a reverse-proxy set up allowing me to access my servers webinterface under https://jellyfin.mydomain.com
without exposing the https port on the container. What I am unsure about now however, is what to do with the two ports for UDP traffic.
By my understanding, a reverse-proxy will only forward traffic which comes to the ports 80 for http and 443 for https. Those are also the only ports my reverse-proxy container has exposed alongside the management interface. As such the 2 udp ports will not be reachable under my jellyfin domain.
How can I change this or is this even an issue?
Hello, I have a question regarding the usage of a reverse-proxy which is part of a docker network.
I currently use Nginx Proxy Manager as a reverse-proxy for all my services hosted in docker. This works great since I can simply forward using each containers name. I have some services however (e.g. homeassistant) which are hosted separately in a VM or using docker on another device.
Is it possible to use the same reverse-proxy for those services as well? I haven't found a way to forward to hosts outside of the proxies docker network (except for using the host network setting which I would like to avoid)
@Scrath
@lemmy.dbzer0.com