CS2

It has a native linux client: https://x0.at/I1ZV.png

NocoDB.

DuckDNS is just unreliable, I’ve found. Try HurricaneElectric; https://dns.he.net/

You’re exposing your jellyfin instance to a single IP, your VPS. That’s what a reverse proxy is.

You block all communication from any IP but local, and your VPS IP from jellyfin, and forward web traffic from your VPS to your jellyfin instance. It’s not the same as exposing your jellyfin instance directly. Not sure why I have to explain that…but here we are, I guess.

We are. I read I feel like committing secrets to a config file instead of .env is a terrible idea. as I feel like committing secrets to a .env is a terrible idea..

Muh bad.

The entire point of .env files are to separate secrets from code. Its specifically the usage for which they were created.

For sure. I’m likely gonna take a look at it this weekend.

I think you’re seriously underestimating the size of this job. This is the work of 4-5 people over several weeks to even upwards of a month. PBX alone is a real PITA to get setup and to manage. Then you actually have to train your people on how to use the infrastructure you just setup for them.

Like you said, they’ve been operating one way for two decades and now you’re completely uprooting that on top of having to setup and manage everything.

You’re underestimating this.

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.