Live connection diagnosis

Tailscale Remote Access Troubleshooter

Use guidance designed for an overlay path instead of a meaningless public open-port verdict.

Tailscale remote access troubleshooter

Tailscale is an overlay network. Connection Vitals does not manufacture a public-port failure for a path that is not supposed to expose one.

Measured evidence first
Detected public IPChecking…
IP version—
Network—

The public IP is shown as context, but Tailscale connectivity is not verified by probing that public IP.

What are you trying to verify?

Why a port checker is the wrong first test for Tailscale

Tailscale creates an overlay between enrolled devices and can work through NAT without a traditional inbound port-forwarding rule. Troubleshoot device enrollment, connectivity inside the tailnet, ACL/policy, local service binding and host firewall before touching public port forwarding.

Public port forwarding is usually not the first Tailscale check

Tailscale documents that NAT traversal normally allows devices to connect without manually opening inbound firewall ports. When a direct peer-to-peer path cannot be established, Tailscale can fall back to a DERP relay.

That means a generic public port checker can be irrelevant even when Tailscale remote access works. Start with device status, the destination service, access policy and host firewall inside the tailnet.

Remote access hub · RDP port checker · Remote-access guide

Official reference: Tailscale firewall documentation.