

I generally stick with the main TLDs. Like com or net.
.com is fairly cheap and won’t be on any blocklists, where some other TLDs can be.
But if you’re in the EU then .eu probably makes sense to use.
He/Him, Bi Furry Boi


I generally stick with the main TLDs. Like com or net.
.com is fairly cheap and won’t be on any blocklists, where some other TLDs can be.
But if you’re in the EU then .eu probably makes sense to use.


There have been a few major ones this year, I’m sure they are fixed at this point though. https://app.opencve.io/cve/?vendor=jellyfin


Plex uses a code signin system where you open the app on your phone or just a browser, and enter the code there.
So there’s no typing/entering anything on the TV at all.


Jellyfin has plenty of issues with public instances too. It’s just the reality of exposing to the public internet, unless it’s something that has a lot of dedicated work going into security it’s going to have problems.


If it breaks I either fix it (often it’s just an issue where the new version needs extra config added), or roll back to a backup and pin the old version temporarily if it really went wrong and I can’t recover otherwise.
Backups run early AM before any auto updates start, and no one is using services and changing data then, so nothing should really ever be lost by rolling back.


It’s easier to setup and use for less technical people, also just more widely known.
I run Jellyfin but logging in is definitely a pain, have to manually enter the URL (including https:// for some crazy reason, why doesn’t it just default to it??) and username and password using a crappy TV remote.


Wildcard SSL does help a lot, since every subdomain isn’t broadcast publicly in the issuer logs.
I’m re-thinking a few things, mostly moving exposed services onto a VM or two that are on their own VLAN, and don’t contain any important data (it would be my website, gameservers like Minecraft, etc…). I might move to podman as well so nothing has a possibility of running as root, docker can run rootless but that setup seems more confusing to me.
I already use a VPN via Wireguard on my router for access to my private services when out of the house, so my changes are just separating the public from the private as much as possible on the server side of things…
Essentially if someone manages to drop a crypto miner or something on my website that’s fine, I’ll get an alert pretty quickly through Beszel that the server load is high and I can go roll back a backup or whatever. I just want to make sure there’s no access to anything else for them.