Top
Best
New

Posted by xd1936 2 days ago

Tailscale Services(tailscale.com)
Video walkthrough: https://www.youtube.com/watch?v=mELAg50ljSA
154 points | 33 comments
sharts 1 day ago|
i like tailscale but i notice that i get more weird network blippy latency issues when using it. i used to always have my phone connected to my tailnet so i could use my dns, etc. but always occasionally something won’t load right and i have to refresh again couple of times.

It tended to happen a lot more when switching between wifi / cellular when leaving and entering buildings, etc.

Now I just don’t use it

david_van_loon 18 hours ago||
I've found that using Tailscale on my Android phone became worlds more reliable (as far as the issues you've described) once I stopped using a custom DNS resolver on my Tailnet.
Hikikomori 18 hours ago||
Want to use my pi-hole as DNS though.
thedougd 2 hours ago||
Similar struggle here. I don't have custom DNS, but do use MagicDNS.
TranquilMarmot 1 day ago||
Very cool, I love Tailscale. I use it to connect together a VPS, desktop computer, phone, and a few laptops. My main use case is self-hosted Immich and Forgejo so this is great.
SOLAR_FIELDS 16 hours ago||
Can someone help me understand what this is vs exposing my services via MagicDNS using the tailscale Kubernetes operator? Functionally it looks like a fair amount of overlap but this solution is generic outside of Kubernetes and more baked into tailscale itself? The operator solution obviously uses kube primitives to achieve a fair amount of the features discussed here.
apenwarr 1 hour ago||
(I'm a Tailscale employee) The recent versions of the Tailscale k8s operator actually used a pre-release of the Services feature to do exactly that. So, not much difference. The official Services release is making that functionality available for more use cases (and generally better documented and user friendly).
nickdichev 15 hours ago|||
I’m also curious about this since I’ve been exposing services via their experimental caddy plugin.
smallerize 13 hours ago||
Was the personal plan not always free?
aidos 18 hours ago||
Does anyone use Tailscale in production as the network layer between services? Would be interested about hearing experiences.

We use it for to allow us to connect in from the outside (and user to user access etc), but not for service to service connections.

SOLAR_FIELDS 16 hours ago||
In addition, do people do so in mesh format? Seems expensive to do so for all of your machines, more often the topology I see is a relay/subnet advertisement based architecture that handles L3 and some other system handles L6/L7
Multicomp 18 hours ago||
Works great to connect fly.io apps that are only exposed to flycast private IPv6 addresses. And I think Tailscale services will replace these.

Performance between fly.io web servers in iad region to RDS databases in us-east-1 via subnet routers has been spotty to say the least.

keeda 16 hours ago||
Fascinating to watch Tailscale evolve from what was (at least in my mind) a consumer / home-lab / small-business client networking product into an enterprise server-networking product.
echelon 16 hours ago|
They're morphing into a B2B centicorn, and the consumer-led tooling route was a genius path.

They provided much-needed solutions to annoying problems and did it in a way that made developers love them.

Really smart and well executed.

SOLAR_FIELDS 11 hours ago||
I know they are good at what they do because it's dev tooling that I will actually pay for, which is as many people know, a difficult thing to convince developers to do.
dlisboa 17 hours ago||
If I'm getting this right it's only highly available from a network layer perspective. However if one of your nodes is still responsive but the service that you exposed on it isn't responsive there's no way for Tailscale to know and it'll route the packet just the same? It's not doing health checks like a reverse proxy would I imagine.
defnnn 1 day ago||
This would be great if it supported wildcards for ingress controllers. A service foo would give you foo.tailYYYY.ts.net as well as *.foo.tailYYYY.ts.net.
david_van_loon 18 hours ago||
I'm happy to see this feature added. It's a feature that I didn't quite realize I was missing, but now that I see it described, I can understand exactly how I'll put it to use. Great work as always by the Tailscale team.
subarctic 1 day ago||
This sounds great, I think it's exactly what I was looking for recently for hosting arbitrary services on my tailnet. I figured out a workaround where i created a wildcard certificate and dns cname record pointing to my raspberry pi on my tailnet but this could be potentially simpler
paxys 15 hours ago|
I understand the usefulness of the feature, but find their examples weird. Are people really exposing their company's databases and web hosts on their tailnet?
nickdichev 15 hours ago||
Yes I host web services for my consumption, like miniflux rss aggregator, that don’t need to be on the public internet.

Similarly I’m going to host my small business’ staging database on a home server and expose that on my tail net.

theshrike79 8 hours ago||
How is that different from exposing on the company intranet in general? Or hosting them in a publicly accessible AWS endpoint?
More comments...