2025-05-02, 09:39 PM
(2025-04-15, 12:11 AM)TheDreadPirate Wrote: I answered your question in the other thread. Fill out the known proxy field with the IP of the host running the proxy. Even if it is the same host running jellyfin.
Dashboard > Network > Known proxies
There was a security vulnerability addressed in 10.10.7 that now requires this field be populated for Jellyfin to accept the X-Forwarded headers used by reverse proxies.
Thanks for sharing that solution. It has resolved the problem for me.
I'd previously had the https FQDN in that field.