this post was submitted on 31 Mar 2025
214 points (98.2% liked)

Selfhosted

59955 readers
379 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.

  3. Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.

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

  5. Submission headline should match the article title.

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I already host multiple services via caddy as my reverse proxy. Jellyfin, I am worried about authentication. How do you secure it?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] sugar_in_your_tea@sh.itjust.works 3 points 1 year ago (1 children)

Just make a different API prefix that's secure and subject to change, and once the official clients are updated, deprecate the insecure API (off by default).

That way you preserve backwards compatibility without forcing everyone to be insecure.

[โ€“] merthyr1831@lemmy.ml 4 points 1 year ago

Even just basic API versioning would be sufficient. .NET offers a bunch of ways to handle breaking changes in APIs