Selfhosted

60093 readers

962 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:

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 30 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!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Tailscale Services GA: App-aware connectivity with more control (tailscale.com)

submitted 4 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

[–] WingedObsidian@sh.itjust.works 3 points 4 months ago* (last edited 4 months ago) (1 children)

Love pangolin. Although I wish internal connections would make more sense

[–] hoppolito@mander.xyz 1 points 4 months ago (1 children)

I have long had a switch to pangolin for my homelab services on the roadmap. Can you explain what you mean with internal connections making more sense?

[–] WingedObsidian@sh.itjust.works 2 points 4 months ago

Just minor issue that maybe I’m not configuring correctly but when I use private resources I have to use the Ip instead of the alias. Looked online and it seemed other users were experiencing the same issue of not being able to use the alias. At this point I’m almost thinking it might be easier set up a second traefik container that just handles all the local connections and configure manually. Would love to just type my *.local address and have it be simple like that. Otherwise I love it and everything else it comes with! An alternative could be netbird, but want to see if I can figure out that small tid bit of pangolin first.