Connection Issues

# Nexus Telemetry Cannot Find the Dish

Nexus Telemetry connects to your Starlink dish at 192.168.100.1. If the connection fails, check the following:

# Are you connected to your Starlink network?

Nexus Telemetry needs to be on the same network as your Starlink dish. Verify you are connected to your Starlink Wi-Fi or plugged in via Ethernet.

# Test connectivity to the dish
ping 192.168.100.1

If the ping fails, you are not on the Starlink network.

# Are you using a third-party router?

If you replaced the Starlink router with your own, you need to ensure your router has a route to the dish. Most routers handle this automatically if the Starlink dish is connected to the WAN port.

If you are using Starlink in bypass mode, add a static route:

Destination: 192.168.100.0/24
Gateway:     (your Starlink dish's IP on your network)
Interface:   WAN

The exact steps vary by router brand. Consult your router’s documentation for adding static routes.

# Intermittent Disconnections

If Nexus Telemetry connects but frequently loses connection:

• Check for obstructions: Trees, buildings, or other objects in the dish’s field of view cause signal drops. Use the Obstruction Map in Nexus Telemetry to identify problem areas.
• Check network stability: If your local network (Wi-Fi) is unstable, Nexus Telemetry may lose its connection to the dish even though Starlink itself is working fine.
• Firmware updates: The Starlink dish occasionally reboots for firmware updates. These are normal and typically last 1–2 minutes.

# Firewall or VPN Blocking

Some firewalls or VPN configurations may block the local connection to 192.168.100.1. If you use a VPN:

• Ensure the VPN is configured to allow local network access
• Add 192.168.100.1 to the VPN’s split tunnel exclusion list

# Common VPN split tunnel configuration
Excluded routes: 192.168.100.0/24

# Using Interface Binding (Pro)

If you use a VPN, Nexus Telemetry Pro provides a built-in solution. Go to Settings → Network and enable Bind to network interface. Select the network adapter connected to your Starlink router (e.g. en0). This forces Starlink gRPC traffic through your local interface, bypassing the VPN tunnel at the socket level.

This is the recommended approach; it requires no VPN configuration changes.