Comment on Ways to Expose Services Publicly
frongt@lemmy.zip 5 weeks agoSure, any project designed to be exposed to the Internet. Web servers would be the most obvious.
Comment on Ways to Expose Services Publicly
frongt@lemmy.zip 5 weeks agoSure, any project designed to be exposed to the Internet. Web servers would be the most obvious.
Probably the number one recommendation I see in self hosting communities is to not open ports directly (other than for a reverse proxy). It seems like a common recommendation no matter the service. To be clear: I am a beginner. I know very little about this, but I’ve spent months learning. I can’t say you’re wrong, but I don’t think you’ve made a convincing argument for me to actually understand why Jellyfin is unsafe to expose to the internet compared to any other service.
frongt@lemmy.zip 5 weeks ago
You are welcome to expose it at your own risk. Assess you own tolerance for compromise (personal data compromise, becoming part of a botnet, becoming a host for spam or CSAM) and proceed accordingly.
Yes, that’s exactly what I’ve done. You still haven’t shown me why it’s unsafe. If you can’t, that’s fine. At some threshold or another, nothing is secure. The one thing I know for sure is that that first page, that says it doesn’t recommend exposing a port, does not say what you said it does.
frongt@lemmy.zip 5 weeks ago
It sounds to me like you just have a higher risk tolerance, and if you accept that, that’s okay.