this post was submitted on 20 Feb 2026
74 points (100.0% liked)

Selfhosted

60870 readers
736 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
74
Tailscale Services GA: App-aware connectivity with more control (tailscale.com)
submitted 5 months ago by new_otters_raft@piefed.ca to c/selfhosted@lemmy.world
29 comments fedilink hide all child comments
 

This should be excellent for selfhosters that have all their services in one VM. I haven't tried this myself, but I think this means you can:

  • you can create memorable links instead of memorizing port numbers: jellyfin.foo-bar.ts.net
  • share one service from a machine instead of all of them in a more intuitive way

If you’re new to Tailscale Services, it lets you publish internal resources like databases, APIs, and web servers as named services in your tailnet, using stable MagicDNS names. Rather than connecting to individual machines, teams connect to logical services that automatically route traffic to healthy, available backends across your infrastructure. This decoupling makes migrations, scaling, and high availability far easier, without reconfiguring clients, rewriting access policies, or standing up load balancers. Our documentation has details on use cases, requirements, and implementation.

you are viewing a single comment's thread
view the rest of the comments
[–] avidamoeba@lemmy.ca 11 points 5 months ago* (last edited 5 months ago) (3 children)

- you can create memorable links instead of memorizing port numbers: jellyfin.foo-bar.ts.net

BTW, I'm doing something similar with standard DNS records that point to an internal Tailscale IP. I can go to https://immich.mydomain.com/ which only works if Tailscale is active. Let's Encrypt works too. Obviously the setup isn't automatic but it's automateable for more adept self-hosters.

[–] blanka@lemmy.dbzer0.com 2 points 5 months ago

I do this too. Can recommend.

[–] TheBlackLounge@lemmy.zip 2 points 5 months ago (1 children)

Immich needs this, right? I remember it not working on a tailscale funnel path.

[–] avidamoeba@lemmy.ca 2 points 5 months ago (1 children)

I haven't tried funnel but it works using an internal Talscale IP/host and port. E.g. http://the-immich-host:1234/ if the-immich-host is a Tailscale machine.

[–] TheBlackLounge@lemmy.zip 2 points 5 months ago

Just tried it, Services doesn't work with funnel. You need to be on the tailnet.