Diagnose Connection Problems
Two checks, from the network up. Run them in this order and stop at the first one that fails: it names the layer to fix.
| Order | Command | Answers |
|---|---|---|
| 1 | nfltr status | Can this machine reach nfltr.xyz at all? (DNS, TCP, TLS, the gRPC channel) |
| 2 | nfltr status, nfltr services | How fast is the service, and which of your machines and services are online? |
Prerequisites
- The
nfltrCLI, with this machine enrolled in your account (nfltr config login).
1. nfltr status: the network path
When the relay is not reachable, nfltr status checks the path layer by layer (DNS, TCP, TLS, gRPC) and names the failing one. The output has this shape (the failing row varies):
$ nfltr status
Server: https://nfltr.xyz
Status: not reachable
✓ DNS resolution (grpc.nfltr.xyz) <address>
✓ TCP connect (grpc.nfltr.xyz:443) 12ms
✗ TLS handshake (grpc.nfltr.xyz:443) certificate signed by unknown authority
It exits 0 when the relay is online and 2 when it is not reachable. The first ✗ tells you where to look: DNS (resolver, VPN split DNS), TCP (a firewall that blocks outbound port 443), TLS (a proxy that intercepts HTTPS, a wrong system clock), gRPC (a middlebox that breaks HTTP/2). It also shows this machine's identity: its certificate (machine id, name, relay, expiry), or none, and each problem with the command that fixes it, for example problem the certificate is for relay nfltr.xyz, not relay.lan (the relay this config uses) followed by fix nfltr config set-relay …. --json prints the same for scripts (server, machine, problems).
2. nfltr status and nfltr services: the service and your machines
$ nfltr status
Server: https://nfltr.xyz
Status: online
Latency: 41ms
What is online: nfltr services
machine m-<id>
name laptop
relay nfltr.xyz
not_after <24 hours from enrolment> (valid)
nfltr status says whether the service is up and how fast it answers, and who this machine is there. What your account has online is nfltr services, which uses your key:
$ nfltr services
NAME KIND E2EE DIRECT INSTANCES UP
pg@db tcp e2ee - 2 2
you-home-lan/db tcp e2ee - 1 1
you-build-box - - - 1 1
One row per name you can dial: <service>@<group> for a service published under an organisation group, <agent>/<service> for one that is not, and an agent that declares no service (a node, a listener) by its id. If a machine you expect is missing, the problem is on that machine: run nfltr status there. A rejected key exits 2 and says so; nothing online that this machine may reach exits 3.