ampersandrew

My wife spent about $130 for a year subscription to a service that she figured would always have her favorite show on it, because they own that show. Then like 10 seasons of it left for an exclusivity deal on another service. This was a contributing factor to pushing me into self hosting. Some of it is saving money, but some of it is also making sure you actually got what you paid for.

Yeah, it’s on my to-do list for my domain registrar, but the above was in relation to OPNsense configuration, which I found a solution for.

It does sound exactly like this. However, I’m concerned about following these instructions when my external IP isn’t static. I still have yet to set up DDNS (I believe is the term, for automatically updating my domain’s DNS servers with whatever new IP address my ISP gave me), but this looks like it’s entirely IP driven.

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.

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.

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?

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.

I’m currently only hosting Jellyfin (movies and TV) and Komga (books and comics) on a LAN, but I already bought a domain, and I’ll be exposing them via reverse proxy within the next few weeks; maybe even this weekend if everything goes well. After that, Nextcloud is a must for sharing large files, as Google Drive’s limits are coming up on me fast, and I’ll start test driving Fluxer as a replacement for Discord.

I don’t think I can read books fast enough to make automation attractive either, haha. I break DRM on Calibre with two plugins, books purchased from Kobo, and then organize on Komga after manually dragging the files.

Correct. I have received help from that server in the past, and it’s unusable now. Part of what I hope to accomplish is to replace Discord, or at least offer my friends an off-ramp. Getting started with Discord is way easier, and in the year 2026, I wouldn’t know what other client to use to look for a community that gives me quick help via live chat. I no longer know how to use IRC, I’ve found.

Gotcha, thanks for taking the time to humor me. I never would have guessed.

Maybe you said so in some lingo that’s foreign to me, but what upsets that reputation? What kinds of configurations do they not like, and why is it not set and forget? Sorry for asking for a dissertation, but I never had any idea e-mail could be more complicated than set and forget.

What is your reputation in this context? And what does losing it cost you?

Would you care to give some additional context here? I haven’t had the itch to host my own e-mail, but what kinds of misfortune do you encounter when you’re not in the good graces of Google of Microsoft? And what could land you in that situation?