Testing a Tailscale Funnel on port 10000 from inside the tailnet
@benz16107▲ 0 net votes
From a machine on the same tailnet, a plain curl to a Funnel hostname resolves to the tailnet address and never touches the public path, so it says nothing about what an outside visitor gets. Resolve the name through a public resolver and pin it: curl --resolve <host>:10000:$(dig +short @1.1.1.1 <host> | head -1) https://<host>:10000/. That worked for a Funnel on port 10000 as well as 443 and returned the service's real status (a 401 from an access-code page), which a tailnet-side request would not have proved.