Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

Those aren't pirated copies, those are... lawfully encoded... 4k bluray rips... I made myself... to back up the uh, lawful copies I purchased at MSRP! That's right!

https://dearrow.ajay.app/

The only reason they're that bad is cause it's what people click on. I do agree they look terrible but it's what draws people in.

I refuse to watch videos with a thumbnail showing an open mouth.

Oh my. You're doing it wrong. Exposing the unencrypted connection without the proper security measures is putting yourself at risk. Regardless of how strong you set the password, the connection can still be abused in all manner of ways. If you read the jellyfin documentation, you'd see the developers clearly state you should never do this. You need to put Jellyfin behind server software. Specifically a reverse proxy. I use NGINX. You can setup your connection to be secure this way. You can now also use Cloudflare if you have cache turned off. And if you really wanna go the extra mile, route it behind a VPN. Though this makes it harder for those you share it with or some devices that don't support VPN.

Please revise your connection. If you need help, feel free to reach out.

Don't expose anything directly to the Internet except a VPN with strong auth.

Why not use a reverse proxy to keep everything on port 443 behind your own domain or duckdns? /gen

How are you detecting/monitoring it. I would like to do the same in my server

This is the biggest downfall of Emby/Jellyfin IMO. It's a tradeoff from being reliant on Plex's authentication servers, but requires a lot of technical knowledge to setup correctly (rather than just port forwarding and relying on a strong password).

I've been running Plex on a Pi 3 and now Pi 4 along with multiple other containers with no real problems. I don't transcode obviously but have no issues with performance.

I also installed Jellyfin last week to run side by side but ended up uninstalling as even when idle the memory usage went through the roof.

I'm sticking with Plex for now too. Although there are some grating, persistent issues in basic use, it usually just works.
Swear the UI gets laggier on the TV by the day, Jellyfin was jarring to me how snappy it was in comparison.

Off the top of my head, I can think of 3 ways.

1. Using a VPS and DDNS (I personally do this):
   • Pros: Super easy for others to access, you just give them the address.
   • Cons: Not free. (Oracle free tier might work, but it's unreliable.) But there are cheap VPSs as low as $12/yr that work pretty well. Also, it's a bit harder to setup since you'll need to create a VPN tunnel between your local machine and the VPS.
2. Using tailscale or zeroties:
   • Pros: Free, and easier to setup than a VPS.
   • Cons: People need to install extra apps to access your server.
3. By port forwarding:
   • Pros: Super easy to setup, just need to forward the ports through your router.
   • Cons: You're opening a port to the internet, which is less than ideal. Also, it won't work if you're behind a NAT.

It's easy af, just look up Jellyfin server guide. Basically it's just forwarding a few ports and setting up usernames/passwords for them and you're good to go

Yeah, why is it doing that?

Especially when I'm using the Jellyfin Android TV client. The quality goes from ok to complete shit.

Does it not like mkv files?

Try Usenet, you don't need to worry about a VPN that way