SOLVED: Windows + Caddy + DuckDNS - how do I setup SSL?

[TheDreadPirate]

That is correct.

One thing you do need to set is the "Known proxies" setting in Jellyfin.

Dashboard > Networking > Known proxies.

Put 127.0.0.1, save, restart jellyfin.  This field is required starting with 10.10.7.  Even if the same host running Jellyfin is the proxy.

Otherwise remote clients will appear as 127.0.0.1 in your logs and any bit rate limits you've set won't be applied.

Oh man, is this the answer to the long winded thread I just posted?

https://forum.jellyfin.org/t-windows-cad...eam-limits

Yes.  Starting with 10.10.7, filling out the known proxies field is a requirement due to a security vulnerability that was patched in this version.

https://github.com/jellyfin/jellyfin/sec...-gmhm-rfv9

Due to the fix required to address the vulnerability, Jellyfin will not use the X-Forwarded-For header without an address in the known proxies field.

[MazMan]

That is correct.

One thing you do need to set is the "Known proxies" setting in Jellyfin.

Dashboard > Networking > Known proxies.

Put 127.0.0.1, save, restart jellyfin.  This field is required starting with 10.10.7.  Even if the same host running Jellyfin is the proxy.

Otherwise remote clients will appear as 127.0.0.1 in your logs and any bit rate limits you've set won't be applied.

Oh man, is this the answer to the long winded thread I just posted?

https://forum.jellyfin.org/t-windows-cad...eam-limits

Yes.  Starting with 10.10.7, filling out the known proxies field is a requirement due to a security vulnerability that was patched in this version.

https://github.com/jellyfin/jellyfin/sec...-gmhm-rfv9

Due to the fix required to address the vulnerability, Jellyfin will not use the X-Forwarded-For header without an address in the known proxies field.

As a new Jellyfin user, is there a guide to setting this up “for dummies”.