this post was submitted on 14 Nov 2026
60 points (96.9% liked)

Selfhosted

63822 readers
637 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
 

Hey everyone. This is probably a super noob question, but I'm very much just an amateur when it comes to self-hosting.

I host several services that I access locally through 192.whatever:####, and when I occasionally need remote access, I use Tailscale and access through 100.whatever: ####. The duplicate bookmarks is mildly annoying though.

Can I just buy a personal domain, and have all my services be coolname.com:#### for both local and Tailscale access? Is that as simple a process as I want it to be?

Edit: I appreciate all the comments and I'll probably just use Tailacale's MagicDNS for simplicity, but one or my (unwritten, my bad) goals was to have one URL that works locally and remotely, regardless of Tailscale. I don't leave Tailscale constantly connected because it overheats my phone (which already has terrible battery life).

you are viewing a single comment's thread
view the rest of the comments
[–] sudo@programming.dev 4 points 1 day ago

<hostname>.ts.net should automagically work whenever tailscale is on. You might have to enable something.

If you want more specific, like sub domain names per service, you can set custom DNS records in tailscale to point to a caddy server which routes to the correct port. The caddy server doesn't have to be the same machine as the service if its on the tailnet.

Getting https involved is a bit more tricky. You don't need it because its all over wireguard already, but the browser doesn't know that and will complain. I think official tailscale can distribute ssl certificates across your tailnet but if you're using headscale you'll either need to do that manually or buy a domain and have caddy auth for that domain.