Help
Troubleshooting
Common issues and quick fixes for connector setup and operation.
Connector shows "Disconnected"
Possible causes
- The connector app is not running
- Firewall/proxy blocks outbound WebSocket
- The setup file is missing or not imported
- Gateway URL is wrong or unreachable
What to do
- Open the connector app and copy the latest logs
- Ask your admin to verify the gateway URL is reachable from this machine
- Re-import the latest setup file
Authentication errors
- "Invalid token"
- "Unauthorized"
- "Connector not found"
Re-import a fresh setup file. If your founder admin or Aerospace support reissued the headless/server package, older bootstrap material stops working.
Quick health check
1) Connector app status
It should show Connected and recent logs should be updating.
2) Gateway reachability
Your admin should confirm the gateway URL is reachable and `/healthz` returns OK.
3) Setup file freshness
If a setup file or headless/server package was reissued, download the latest artifact before reconnecting.