No awards are needed, just wanted to share my excitement that while my Jellyfin server still keeps loosing my entire library every 24 hours at least now it has a domain and ssl cert!
That is all. Happy Friday everyone
No awards are needed, just wanted to share my excitement that while my Jellyfin server still keeps loosing my entire library every 24 hours at least now it has a domain and ssl cert!
That is all. Happy Friday everyone
What’s wrong with exposing Jellyfin to the internet?
You really shouldn’t expose anything directly to the internet. It is a security problem waiting to happen. (Assuming it hasn’t already)
This is how giant botnets form.
What security problems?
Bots randomly attack stuff, and if you leave something insecure, they’ll install a bot net node.
Define “insecure”.
Default passwords, old insecure versions of apps and system packages, etc. “Just getting it working” usually leaves things insecure, and you usually need to take things a step further to secure your publicly accessible services.
Not just old insecure, but current insecure too. Plenty of stuff runs fully current but still vulnerable code. Put it behind a firewall.
Sure. My point is that self-hosters tend to let services sit without updates for months if not years at a time. That’s fine if you don’t expose anything to the internet, so keep that surface area as limited as possible.