Comment on Round Two: Can I manage to set up Jellyfin correctly this time?
littleomid@feddit.org 1 day agoIf it doesn’t have to be exposed, then it shouldn’t be exposed. A Webserver should be exposed: Nginx and co are working on it for decades. Jellyfin on the other hand is a much smaller project, and chances for security issues are significantly higher.
dgdft@lemmy.world 1 day ago
Did you read the thread body? Op is using Caddy to reverse proxy.
The smoothbrain top comment is claiming that Jellyfin “wasn’t designed to be exposed to the internet” AT ALL, reverse proxy or not. You’re poking at a strawman here, and putting words in my mouth that I didn’t say.
littleomid@feddit.org 1 day ago
How does reverse proxy help with security? Reverse proxy is mostly there for the convenience.
ITGuyLevi@programming.dev 1 day ago
Umm… Not sure if you are serious but knowledge is meant to be shared so… A reverse proxy isn’t really for convenience, it sits between two networks and proxies traffic according to specific rules. It also has the benefit of masking the origin server a bit (like its IP) and in a lot of cases can be used as a way to ensure traffic going to a server or service that doesn’t support transport encryption actually transverses the internet within a secure tunnel.
littleomid@feddit.org 1 day ago
Yes, that’s why I said mostly. In this context reverse proxy is being used to access different ports via 80/443 from outside. That is not necessarily the use case you’re mentioning.
dgdft@lemmy.world 1 day ago
Sorry, I assumed you were intelligent and sanewashed your comment.
I assumed you were talking about the fact that internal web servers that services like Jellyfin run are often DoSable without a proxy.
Jellyfin is quite literally a web app and perfectly safe to host on the web. Wanna prove me wrong? I’ll happily spin up an instance and throw a $500 bounty on there for you.
littleomid@feddit.org 1 day ago
What the fuck is your problem 😂😂