Yep, that’s why I call that a tradeoff. Far from perfect and yet so much better than nothing.

Pros:

• Likely cuts 99.99% of attacks.
• Nothing to do on client’s end.

Cons:

• Whitelisting must be updated everytime the client address changes.
• Not 100% bulletproof as operators (notably for mobile networks) can NAT multiple connections behind a single publicly addressable IPv4 address.
• Also IP addresses can be spoofed but I doubt that would be a major concern here.

No, not for remote access over the internet.

For a remote and non-technical user I would say IP whitelisting offers a decent tradeoff.

On your end you expose your jellyfin port to internet, but restrict at the router level to your user’s client IP address as soon as you have it. Obviously in practice this works best if the address does not change often.

Oh so there is a proper name for this ! I have had those once in a while since I was a kid, and still get them well into my forties.

I do still remember the anxiety the first time it happened.

KeePass features a built-in synchronization mechanism. I store my password file on google drive for ease of access on multiple devices. I set up triggers (on save, on custom button) to sync between the local copy and the cloud copy, using this guide: https://keepass.info/help/kb/trigger_examples.html#dbsync

Not a turnkey solution, but once setup it works like a charm.

Sysinternals (winternals) tools are so useful ! There is something for everyone there (TcpView, ProcExp are my personal go-tos). MS was well inspired to buy it and hire M. Russinovich.

I like the enthusiasm, but I’m sure you realize why Jellyfin is more suitable for mainstream use. The pretty web UI, user management, watch tracking and device-specific clients are what makes the software actually useful if you want to serve media to “normal” people.