this post was submitted on 23 May 2026
172 points (96.7% liked)

Selfhosted

59444 readers
1305 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
[–] nibbler@discuss.tchncs.de 3 points 13 hours ago* (last edited 13 hours ago) (1 children)

If client certificates and basic auth is not supported by jellyfin:

  • reverse proxy
  • strong random subdomain
  • wildcard certificate
  • tls1.3 only
  • doh/dot only

1-3 make random scanners unable to find your service, 4&5 even hide it from your ISP. Dot/doh service will still know your subdomain, so be your own dot/doh ! :D

[–] Jason2357@lemmy.ca 2 points 9 hours ago (1 children)

I'm no expert, but an unguessible URL path is similar but not visible to DNS. Could do both.

[–] nibbler@discuss.tchncs.de 1 points 1 hour ago

If jellyfin Clients can do URLs, sure