Not unless the reverse proxy adds some layer of authentication as well. Something like HTTP basic auth, or mTLS (AKA 2-way TLS AKA client certificates)

For nginx: https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-http-basic-authentication/

so if I add a user ”john” with password “mypassword” to video.example.com, you can try adding the login as: “https://john:mypassword@video.example.com”/

Most HTTP clients (e.g. browsers) support adding login like that. I don’t know what other jellyfin clients do that.

The other option is to set up a VPN (I recommend wireguard)

I did not expect this great a read…

It took me a while to finish, but I am impressed by both the style and substance, and the way so many disparate subjects are combined so well in a cohesive whole.

Thanks for posting.

They probably mean this: https://mycroft.ai/blog/update-from-the-ceo-part-1/

Read a publisher called Wired

Look inside

No wires…

You should do application level backups and put those in backblaze b2:

• for postgres look here.
• look at all the software you’re running and what they say about making backups.
• for files that don’t change often, making a an archive (with tar) is probably good enough. But if it changes during making the archive, the backup will be inconsistent.
• think about your RPO: how much data are you willing to loose in case of a crash? 1 day? 2 hours? 15min? Schedule your backups to be at least as frequent.
• Don’t forget to test your backups! Otherwise you’ll only find out that the backup is unusable when you need it most…