Selfhosted
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
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.
-
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:
- 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!
view the rest of the comments
Look at their MagicDNS for this. It uses the hostname of the system along with your tailnet to allow you to do just this
This is the correct answer. You can even use it to force all the devices in your tailnet to use the same DNS server, and it's really quite easy to host a sinkhole with either PiHole, AdGuard Home, or my preference, dnscryptproxy. Also works with just the hostname if you want. I.E.
ssh MyLinuxBoxworks just as well asssh MyLinuxBox.whatever.ts.net.If you want the service publicly accessible through the wider internet (the person doesn't even need TS to access the website), check out TS Funnel.
The downside to the
.ts.netapproach is that you need to install multiple TS clients if you want multiple subdomains. Typically one per service.There are projects like TSD-Proxy that help with that. It makes it so you only use one Docker container instead of having to make a sidecar container for every service.
Then you also have to resolve
*.tailnet.ts.neton your LAN's DNS and that's it. Unless you ever want to use something other than Tailscale, that is.Ooooh. I guess I have some reading to do.
So this definitely seems like the easiest solution, and MagicDNS is on by default, and the normal 100... address works fine, but no combination of the short or full domain seem to actually work. Not homeserver:#### nor homeserver.tail#.ts.net:#### nor even 100.100.100.100:####. Maybe it's an issue with Unbound or something. Blargh.
Not trying to sound like an ass, promise. Have you declared those routes in Tailscale? There are two methods of doing this. One uses pathing, with
--set-path, and not everything supports serving on a path without changing the base URI of the application you're trying to reach. It looks like you're sticking to ports, but I haven't see anyone ask how you're declaring this with thetailscale servecommand.And did you add a funnel, or just
tailscale serve?tailscale funnel --bg http://localhost:1234/This is different, and I believe they are mutually exclusive.
The funnel would show as https://hostname.tailnet-name.ts.net/ to anyone online without needing tailscale, and that sounds like what you're after as far as deduplicating bookmarks. If I'm not mistaken this only supports 443/8443/10000 ports, however. It's also hanging free in the breeze for anyone to get to if they know the URL.
Again, sorry if this is asking redundant questions or anything.
What are you testing MagicDNS with? What are the DNS settings? What does trying
dog myhost(ordig, or usingabout:networkingin a Firfox derived browser (maybe Chrome too?) if you prefer) tell you? For reference, on a Linux host (I don't remember exactly, so don't quote me), you should se something like this in/etc/resolv.confSo I was doing this from the (emulated?) terminal on my Android phone, and dig just returned command not found. I just got off work and moved to my desktop running Fedora, and on my desktop MagicDNS addresses work. Which I guess narrows things down.
On my desktop, dig returns
My resolv.conf is pretty similar. The namesever I'm pretty sure is correct for systemd reasons.
I appreciate the help, but realistically the answer to "Is that as simple a process as I want it to be?" is no, not quite, at least at my knowledge level lol. I'll do more documentation reading in the meantime.
Interesting. Does trying to simply ping
myhostormyhost.xxx.ts.network?On Android (well, GrapheneOS) both return temporary failure in name resolution.
Pinging the Tailscale IP (the 100. one) returns 100% packet loss even though opening 100.whatever:#### works in a browser.
Ok, I think I am beginning to understand the issue. Can you try resolving the domain in your browser? If it's a Firefox derivative, you can go to about:networking, and it gives you the ability to resolve a domain in the browser. Some Chrome based ones should have similar features, but YMMV.