How do you keep track of URLs of services for your tailnet?
retained text
I run a few services on my Tailnet, and I kept running into a small but annoying problem when sharing them with other people in the family. For example, I might have something like: `rpi4-8gb.tailxxxyyyzz.ts.net:2283` but what I'd really like to give someone is: `immich.domain.me` Normally I'd solve this with a reverse proxy sitting in front of the service. But the service is not really exposed to the internet, just the tailnet. Plus, I didn't really want to set up and keep updating another reverse-proxy configuration + DNS setup every time I moved something around (like when I am upgrading the OS on the machine). So I built a small service called **Red** (stands for REDirection) to scratch that itch. The basic idea is simple: point a domain/subdomain at Red, and Red redirects the request to whatever backend I've configured for it. For example: `images.domain.me` -> `rpi5b1-16gb.tailxxxyyyzz.ts.net:20283` The useful part for me is that the URL that people need to remember doesn't need to change when the machine/port in the backend changes. Another problem was - I am part of a friend's tailnet too and his hostname was also similar to `rpi4bxxx.tailaaabbbcc.ts.net:2283` (he copied my pattern of hostnames) and that was confusing too. So this setup solved that too. I'm curious how other handle this particular situation of moving services among machines (or changing ports). Do you just put everything behind a reverse proxy on the homelab? Use Cloudflare Tunnel/Tailscale Funnel/Something else? Do you guys actually move the services around enough to have this problem in the first place? I'm mainly interested in how people solve the problem. I built Red for myself first, but I'm wondering whether this is a problem other people actually run into.
document fetched 2026-10-01 00:33 · canonical https://reddit.com/r/selfhosted/comments/1wtrvwl/how_do_you_keep_track_of_urls_of_services_for