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.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 7 days old, your post is exempt from this rule as long as you continue to engage in comments.
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
The hard part about Jellyfin is that it requires your own domain and some more self-hosting knowledge that a hobbyist might not have yet.
It's not a super hard transition, but it took me a few months on/off to learn the basics of hosting a website from my house.
I'm still trying to figure out headscale on a VPS so I can mask my home IP
I have my own domains, but I do not use them for Jellyfin. I use Jellyfin on my lan or over my personal VPN.
That means it can't be shared (easily) with others. That's the appeal of Plex and the reason why switching entirely to Jellyfin is not an easy thing to do.
Exactly, I am not going to troubleshoot VPNs with my mother in law when they have an issue.
that's valid, but would you rather spend $8/year on a domain and spend an hour setting it up, or pay a monthly subscription to a closed source plex server?
Also, there's *arr stack applications for helping non-technical users get set up on your jellyfin server, even helping them get set up with request apps too. JFA-GO is also a jellyfin native option for sending user invites.
Oh, I didn't mean to say I was using Plex there. Jellyfin + domain + reverse proxy is what I do for both Jellyfin and Seerr. I was just saying people who say "wireguard is the only way to go" aren't taking into account all workflows, like sharing with family and having them connect via their TVs.
I also just don't want family and friends on my home network all the time, haha.
Makes sense!
wg-easy. Makes Wireguard dead easy.
So all the people who want to use your Jellyfin server have to deal with a VPN first?
That's my point. Plex was easily accessible for friends and family with minimal setup. Jellyfin requires a bit more knowledge.
You're making it sound like I'm making my users walk a mile on burning coals! Yes, I do expect them to be able to be able to tie their shoelaces, install an application and scan a QR code. It's not like they're not getting anything in return for such "trouble". ;)
Most people should be using a VPN and not exposing these things to the internet at large via proxies or port forwards.
Right, but if you're hosting Plex then you've likely shared it with friends/family. Jellyfin isn't as easy to share.
It's also pretty insecure so host over the web at your own risk.
Is it? I've heard it is fine as long as you are running a reverse proxy, using https, and following the conventional wisdom.
There are a lot of unsecured endpoints in the system, the devs know its an issue.
Give Netbird a shot. I set it up in like two hours. Much easier than my failed attempt at headscale+tailscale.