![]() |
New Jellyfin Server/Web release: 10.10.7 - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Announcements (https://forum.jellyfin.org/f-announcements) +--- Forum: Project Announcements (https://forum.jellyfin.org/f-project-announcements) +--- Thread: New Jellyfin Server/Web release: 10.10.7 (/t-new-jellyfin-server-web-release-10-10-7) |
RE: New Jellyfin Server/Web release: 10.10.7 - cursedmuffin - 2025-04-06 Hi! My setup was working up until this update. However I can no longer access Jellyfin through my reverse proxy (LAN IP works fine). I have it setup with Caddy, and following the new recommendations, had set Dashboard > Networking > Known proxies to the localhost loopback IP range (127.0.0.0/26), but I get a blank page whenever I try to access my domain through a web browser. I run Caddy in a container, however it uses the host's network, so its IP should essentially be that of the localhost. I am totally lost. Am I doing something wrong? Edit: I have also tried using the IP of the Podman network that the Jellyfin container uses, but it didn't work either. Edit 2: All my previously configured clients still work and do produce logs in the remote proxy when reproducing media, but accessing the domain through a browser still returns a blank page. RE: New Jellyfin Server/Web release: 10.10.7 - RBetting77 - 2025-04-06 (2025-04-06, 12:04 PM)cursedmuffin Wrote: Known proxies to the localhost loopback IP range (127.0.0.0/26), but I get a blank page whenever I try to access my domain through a web browser. I run Caddy in a container, however it uses the host's network, so its IP should essentially be that of the localhost. What's the IP of your reverse proxy? Use that IP. To be safe, you can use the subnet in the known proxies: [ip]/24 RE: New Jellyfin Server/Web release: 10.10.7 - TheDreadPirate - 2025-04-06 (2025-04-06, 12:04 PM)cursedmuffin Wrote: Hi! My setup was working up until this update. However I can no longer access Jellyfin through my reverse proxy (LAN IP works fine). Please start a separate thread and provide what you've put in the known proxies field. RE: New Jellyfin Server/Web release: 10.10.7 - cursedmuffin - 2025-04-06 Using my LAN's IP with subnet mask seemed to do it. Thank you! On another note, is there any chance that this configuration setting be included as a environment variable in the Docker image? Just so that it can be set in an unattended manner in the future. RE: New Jellyfin Server/Web release: 10.10.7 - theguymadmax - 2025-04-06 (2025-04-06, 04:16 PM)cursedmuffin Wrote: On another note, is there any chance that this configuration setting be included as a environment variable in the Docker image? Just so that it can be set in an unattended manner in the future. Automated installs are not supported. Possible options for that may be discussed after the GHSA gets publicly released in 6 days. RE: New Jellyfin Server/Web release: 10.10.7 - Austin - 2025-04-07 I just ran this update. My Jellyfin is behind cloudflare tunnels (technically a reverse proxy). I did not need to update my known proxies setting for those curious. RE: New Jellyfin Server/Web release: 10.10.7 - kf3 - 2025-04-08 Newbie here! I just managed to setup my Jellyfin-server on my Mac with DuckDns and Caddy with a lot of help from ChatGPT. I updated to 10.1.7 the other day and now when I go to my URL I come to the wizard registration page. What shall I do with the settings on Jellyfin and in my Caddyfile? Thanks for all the help in advance! RE: New Jellyfin Server/Web release: 10.10.7 - TheDreadPirate - 2025-04-08 (2025-04-08, 07:00 AM)kf3 Wrote: Newbie here! I just managed to setup my Jellyfin-server on my Mac with DuckDns and Caddy with a lot of help from ChatGPT. Please start a separate thread in the troubleshooting section. RE: New Jellyfin Server/Web release: 10.10.7 - leonida92 - 2025-04-08 Code: *.example.com { This is my caddy configuration for jellyfin using cloudflaredns module. My caddy LXC IP is 192.168.1.20. When I enter this IP in trusted proxies, Jellyfin shows only the caddy IP for every device connected through it. I don't know where to start to troubleshoot this issue. It was working fine before the update without specifying the trusted proxies. Any help on where should I get started? Maybe I should mention that I have configured adguardhome dns as the DNS for tailscale which redirects to the caddy ip. I only access my services outside of my local network via tailscale. RE: New Jellyfin Server/Web release: 10.10.7 - stephany - 2025-04-08 https://jellyfin.org/docs/general/networking/#known-proxies |