Xanza

I respect it.

Nice! I'll give it a try.

Here I am just glad I'm not the only one. lol.

I'm torn between this being fucking genius, and a terrible idea all at once.

EDIT: Requires ngx_http_auth_request_module. * Caddy4lyfe. *

There are two routes. VPN and VPS.

VPN; setup wireguard and offer services to your wireguard network.

VPS; setup a VPS to act as a reverse proxy for your jellyfin instance.

Each have their own perks. Each have their own caveats.

It really doesn't matter how long your media is, it matters the specific conditions you're changing. Encoding takes time, and it's outrageously stressful on a CPU. It's still going to take a long time versus using a GPU.

These people seem...pretty stupid tbh. Maybe they don't understand what fail2ban is, or what it does, but you should absolutely use fail2ban. Security is objectively better by just having it enabled than not for any service, not just jellyfin.

Excellent setup. It's the one I use as well.

I wouldn't setup fail2ban in a container. Install it on the host system.

I would like the transcoding to be done on the server side

Unless your server has access to a GPU, and uses WebGL to be able to utilize that GPU via web tech, I don't recommend doing this at all. Gonna take a dozen hours to encode via CPU...

That's capitalism, baby! /s

Def agree.