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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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
Jellyfin needs to partner with someone people can pay a very low and reasonable and/or one-time fee to enable remote streaming without the fuss of setting up either dangerous port-forwarding or the complexity of reverse proxies (paying for a domain-name, the set-up itself including certificates, keeping it updated for security purposes).
And no a VPN is not a solution, the difficulty for non-technical users in setting up a VPN (if it's even possible, on smart-tvs it's almost always not, and I don't think devices like AppleTV and other streaming boxes often support them) is too high and it's an unwanted annoyance even for technical users.
I'm not talking about streaming video's through someone else's servers or using their bandwidth. I'm talking about the connection phase of clients and servers where Plex acts like an enhanced dynamic DNS service with authentication. They have an agent on the local media server which sends to the remote web service of the third party the IP address, the port configured for use, the account or server name, etc. When a client tries to connect they go to this remote web service with the servername/username info, the web service authenticates them then gives them the current IP address and any other information necessary. It then sends some data to the local Jellyfin server about the connecting client to enable that connection and then the local media Jellyfin server and the client talk directly and stream directly.
Importantly the cost of running this authentication and IP address tracking scheme would be minimal per Jellyfin server. You could charge $5/year for up to 20 unique remote clients and come out ahead with a slight profit which could be put back into Jellyfin development and things like their own hosting costs for code, etc. Even better if they offer lifetime for this at $60-$80 they'd get a decent chunk of cash up-front to use for development (with reasonable use restrictions per account so someone hosting stuff in Hetzner or whatever and serving 300 people with 400 devices will need to pay more because they're clearly doing this for profit and can afford to throw some more money at Jellyfin).
Until Jellyfin offers something that JUST WORKS like that it's not going to be a replacement for Plex, whatever other improvements they offer to users it's still a burden for the server runner to set up remote streaming in a way that isn't either incredibly dangerous (port forwarding) OR either involves paying money to third parties AND/OR the trouble of running your own reverse proxy and/or involves walking users through complicated set-up process for each device that you have to repeat if you change anything major like your domain name when using a VPN.
Umm AppleTV has a Tailscale app and it's dead simple to set up, so I would argue that it is a solution.
That's what I do. Jellyfin + Tailscale + Apple TV box. It works like a charm.
Authelia maybe?
Interesting project. Thanks for the link and I do appreciate it and could see some very good uses for that but it's not quite what I meant.
Unfortunately as it notes it works as a companion for reverse proxies so it doesn't solve the big hurdle there which is handling secure and working flow (specifically ingress) of Jellyfin traffic into a network as a turn-key solution. All this does is change the authorization mechanism but my users don't have an issue with writing down passwords and emails. Still leaves the burden of:
Which is a hassle and a half for technically proficient users and the point that most other people would give up.
By contrast with Plex how many steps are there?
By contrast this still requires the hoster set up a reverse proxy (major hassle if done securely with certificates as well as an expense for a domain which works out to probably $5 a year), to then have their users point their jellyfin at a domain-name (possibly a hard to remember one as majesticstuffbox[.]xyz is a lot cheaper than the dot com/org/net equivalents or a shorter domain that's more to the point), auth and so on. It's many, many, many more steps and software and configurations and chances for the hosting party to mess something up.
My point was I and many others would rather take the $5 we'd spend a year on a domain name and pay it for this kind of turn-key solution for ourselves and our users even if provided by a third party but that were Jellyfin to integrate this as an option it could provide some revenue for them and get the kinds of people who don't want to mess with reverse proxies and certificates into their ecosystem and off Plex.