Known limitations
These are the things Nexus Telemetry Fleet does not do during early access, with what to do about each.
A fleet server on your own servers is by application
A fleet server on your own servers is a private deployment. It is installed with Nexus Telemetry engineers under an annual licence. See Private deployment.
One session per user
A user has one signed-in session. Signing in from a second browser ends the first, and the first browser is returned to the sign-in page at its next request.
Give each person their own user rather than sharing one. See Users and roles.
Listening ports on a collector
A collector serves 2 web pages of its own. The setup page, for enrolling the
collector from a browser, listens on 127.0.0.1:41700. It is on by default
on macOS, Windows and Docker, and off by default on the Linux packages. The
onboard status page, for people at the site, listens on port 9210 once a
user enables it.
Neither is reachable from outside the site. The setup page accepts connections from the collector’s own host only. The onboard status page accepts connections from private addresses only.
Where policy forbids a listening port, both can be turned off. See Setup page and Onboard status page.
Third-party network lookup
By default the collector asks a public lookup service which internet provider the site’s public address belongs to. That sends the site’s public address to a third party, which some security reviews do not allow.
The collector setting NF_CONNECTION_ASN_MODE=off stops the lookup. The carrier, its
name and the site’s public address are then not reported, and the collector
never reports a failover to a backup connection. Every other reading
continues. See Data
sent.
Host network for a Docker collector
The Docker command the dashboard generates includes --network host, which
gives the container the host’s own network. Without it, the collector reads the
container’s network instead of the host’s: it cannot see the real routes or
a VPN, so it cannot name the carrier or detect a failover.
Do not remove the flag from the command. See Docker.
Starlink account data
A collector reads the terminal on the site network: its telemetry, sky map, position, self-test and service state. Nexus Telemetry Fleet does not read the Starlink account: service lines, plans, data pools and billing. Reading the account through the Starlink enterprise API follows early access.
The terminal itself answers 3 of the questions an account is asked. Whether service is restricted where the terminal is: the Degraded state with the cause restricted by policy. Whether the site has moved to its backup connection: Degraded with on backup carrier. Whether a terminal is drifting from its own normal: Warning with latency above baseline or drop rate above baseline, judged against that terminal’s own recent readings. See States.