this post was submitted on 23 May 2026
151 points (96.9% liked)

Selfhosted

59558 readers
685 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Assuming the user will not be connecting over vpn, but is both remote and non-technical, how would you expose Jellyfin to them securely?

you are viewing a single comment's thread
view the rest of the comments
[–] EncryptKeeper@lemmy.world 11 points 5 days ago (2 children)

The biggest problem with that Jellyfin to this day is that you can’t.

Seems like every new open source selfhosted app implements OIDC compatibility, but for some reason, I can only assume is technical debt, Jellyfin hasn’t.

[–] Strit@lemmy.linuxuserspace.show 2 points 5 days ago (1 children)

Jellyfin had a third party plugin for OIDC. It was archived recently, but I heard Jellyfin has plans to implement it directly into the software. 🤞

[–] EncryptKeeper@lemmy.world 0 points 4 days ago* (last edited 4 days ago) (1 children)

The plugin was neat, but if the clients don’t support it, it’s pretty much useless.

[–] Strit@lemmy.linuxuserspace.show -1 points 4 days ago (1 children)

Mobile clients should use QuickConnect for it (statement by the sso plugin maintainer). Else it should work with everything that uses the WebUI.

[–] EncryptKeeper@lemmy.world 1 points 4 days ago* (last edited 4 days ago)

Quick connect is not SSO. Because the topic is about non-technical end user friendly solutions, this isn’t a great one because this requires your user to login using a web browser on a different device and then use that for the quick connect and it’s just more clunky than it should really be.

It’s honestly easier in this situation to just configure your end users device with a mesh VPN like Tailscale or Netbird and then all they ever have to do is login with whatever password you gave them.

[–] kiol@discuss.online 0 points 5 days ago (1 children)

What exactly about jellyfin makes this oidc style access more difficult to manage?

[–] EncryptKeeper@lemmy.world 1 points 5 days ago (1 children)

Jellyfin just doesn’t have it, period. There’s a third party plugin that will kind of tack it on to the Webui, but none of the Jellyfin apps will work with it.

[–] kiol@discuss.online 1 points 5 days ago