+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Getting different results when using nginx vs portforwarding (/t-getting-different-results-when-using-nginx-vs-portforwarding)
Getting different results when using nginx vs portforwarding - Chop1n - 2024-06-13
Hello, I've had nginx running a reverse proxy for jellyfin and it has been working great, but today i noticed that when i access jellyfin via my domain(pointed to nginx) it directs me to jellyfin and allows a login, but no libraries show up. If i instead use my local ip and go to port 8096 it works as expected, it also works as expected if i go public-ip:8096, now I'd rather use nginx than opening port 8096, what could be causing this? For nginx i am using nginx-proxy-manager
I have noticed that requests that are made via local and public ip show up in logs as:
Code:
Emby.Server.Implementations.HttpServer.WebSocketManager: WS 192.168.1.228 requestBut requests made via nginx show up as:
Code:
Emby.Server.Implementations.HttpServer.WebSocketManager: WS 192.168.1.1 requestBoth nginx-proxy-manager and jellyfin are running in docker containers and are currently on the same docker network.
Jellyfin version: 10.9.6
I am stumped right now and don't know what steps to take to debug this, I am open to all suggestions.
Thanks in advance!!!
RE: Getting different results when using nginx vs portforwarding - TheDreadPirate - 2024-06-14
Do you have more than one jellyfin container? Did IPs change?