posted in Selfhosted
Ways to Expose Services Publicly
I want to expose my services publicly on my own domain name, how would you guys do that?
I have seen people using Cloudflare, but I don’t want to use Cloudflare out of principle. I have also seen stuff on caddy and frp that I’ve done some rough researching.
What do you guys do?
I recently switched to Netbird on a VPS (on Vultr). Their reverse proxy is super easy to set up / self host. They also offer a free version that works pretty good too, I just wanted to make it difficult for myself (thats the whole point of self hosting, right? )
Replying to @RanchBranch@anarchist.nexus
I have seen netbird pop around every now and again. I might try out their cloud free version first and if I like it I might try self hosting it.
So you host netbird on a vps you rent and that is used for reverse proxy? So with that reverse proxy I can have my home server be publicly accessible and I can have friends log in to my jellyfin server without having to connect to my tailnet.
My last concern is security. How is this set up good for making sure I don’t just get constantly botted and exploited?
Replying to @pineapplelover@lemmy.dbzer0.com
Opening jellyfin up publicly is kind of asking for trouble if you ask me. I haven't done so myself, but seen enough on this community and elsewhere to know that it's probably not a good idea.
Replying to @innocentzero@kbin.earth
By all means correct me if you know more, but what I tend to see is one or two people here saying that Jellyfin devs don’t recommend exposing it publicly, only to be corrected by looking at the actual documentation. I suspect those cautioning against it are on outdated information and that Jellyfin carries much the same risk as exposing any other service.
Replying to @ampersandrew@lemmy.world
but what I tend to see is one or two people here saying that Jellyfin devs don’t recommend exposing it publicly
I think what the devs are saying is ‘don’t expose Jellyfin to the public in an unsafe manner’. I don’t run Jellyfin, but can confirm what you’ve read here. In that vein, don’t expose anything to the public in an unsafe manner.
Replying to @irmadlad@lemmy.world
There is no safe manner of exposing jellyfin.
Replying to @frongt@lemmy.zip
Again, I do not run Jellyfin, but what you’re saying seems contradictory to what the devs are implying: here and here. Since I lack the hands on experience, I will leave the issue with the experts.
jellyfin.orgNetworking | JellyfinAs a server software, Jellyfin offers different services over the network.Replying to @irmadlad@lemmy.world
That first page says exposing it to the Internet is “not recommended”. Putting a reverse proxy in front of it does not meaningfully change the security posture. A malicious request to http://jellyfin.homelab.com/exploitable-page will be sent to jellyfin in effectively the same way, whether through a reverse proxy or not. You would need a WAF set up specifically to look for relevant exploit attempts.
github.com/jellyfin/jellyfin/issues/5415
Those are some outstanding known vulnerabilities, most of them unfixed. They are not particularly severe, but it shows that thorough security is not a priority for the jellyfin devs.
GitHubCollection of potential security issues in Jellyfin · Issue #5415 · jellyfin/jellyfinCollection of potential security issues in Jellyfin This is a non exhaustive list of potential security issues found in Jellyfin. Some of these might cause controversy. Some of these are design fla...Replying to @frongt@lemmy.zip
It says exposing a port directly to the internet is not recommended; do you know of any project that would recommend directly exposing a port? What is meaningfully different here?
Replying to @ampersandrew@lemmy.world
Sure, any project designed to be exposed to the Internet. Web servers would be the most obvious.
Replying to @frongt@lemmy.zip
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.
Replying to @ampersandrew@lemmy.world
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.
Replying to @frongt@lemmy.zip
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.
Replying to @ampersandrew@lemmy.world
It sounds to me like you just have a higher risk tolerance, and if you accept that, that’s okay.