TrueNAS / FreeNAS Remote Access Test
Find whether the problem is local service access, the public TCP path, upstream NAT or simply a relay/overlay path that should not expose a port.
TrueNAS / FreeNAS remote access diagnosis
Choose whether you use an overlay/VPN, DDNS/reverse proxy, managed remote-access path or direct port forwarding before running a public probe.
The public IP shown here is detected from this browser request. External probes are restricted to that same public IP.
TrueNAS remote access is primarily a private-access problem
TrueNAS documentation recommends that the storage appliance itself is not exposed directly to the internet. Its remote-access guidance covers Tailscale, ZeroTier and WireGuard-style private paths, which do not need a public service port to appear open.
Use guidance mode for Tailscale, ZeroTier or WireGuard
Verify the private-network endpoint, routing and destination service inside the overlay/VPN. A public TCP probe cannot prove that path.
Use the TCP probe only for a deliberately published service
If you intentionally expose an application through a hardened reverse proxy or another public TCP endpoint, test that specific public port. Keep TrueNAS administration itself on a private path where possible.
For a general NAS decision tree, return to the NAS Remote Access Test. For Tailscale-specific failures, use the Tailscale troubleshooter.
Official reference: TrueNAS remote-access documentation.