Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
That's a you/network problem not a jellyfin problem. I run it exposed via a reverse proxy the sane way I expose Plex. I'm not using their bullshit proxy.
If you truly think the average tech illiterate person (the overwhelming majority of people on this planet) is going to understand/be okay with the hoops needed to view contents of a shared jellyfin server then there's no more conversation to be had.
How is it any different to viewing a shared Plex library to the end user?
They have a reverse proxy setup, so their family or friends would simply enter that url into a jellyfin client and sign in.
So yeah, I think an average tech illiterate person can do that
With a reverse proxy there's no need for hoops unless you add some authentication mechanism on top of that. I use reverse proxies for several things so that they flow through filtering like crowdsec or fail2ban. It just routes the single port to the device on question as is. The idea is to make it indistinguishable from a fully exposed port to the user. Just have to make sure whatever system runs the reverse proxy is secured. I always make sure that nothing significant is on the system that is exposed to the internet other than the reverse proxy server and all other ports are closed internally and externally. Ideally a device that has multiple Ethernet ports works well so you can keep an ssh port open on the internally facing ethernet port for troubleshooting. Nice if they are 2.5Gbit or 10Gbit ports, too, since they route a lot of traffic. But not needed.