Skip to main content

Connectivity

Common problems and solutions if you are experiencing issues when connecting to your Rover.

roverctl fails with i/o timeout​

Cause​

This means that the roverd API on the Rover cannot be reached.

Sanity Checks​

  • Is the Rover powered on and does its display show its name and index?
  • Did you specify the correct Rover index?
  • Are you connected to the ASE network?
  • Is the network experiencing high load?

Trouble Shooting​

Confirm the Debix is Up​

First, see if the Rover is reachable on the network by using ping. Use the hostname. For example, for Rover 7:

# Ping Rover 7
ping rover07.local

# Expected output: (IPs may differ)
64 bytes from 192.168.0.107: icmp_seq=0 ttl=64 time=64.046 ms
64 bytes from 192.168.0.107: icmp_seq=1 ttl=64 time=4.771 ms

If you do not see the expected output, this indicates that the Rover cannot be reached on its IP. Possible causes are:

  1. The Rover is connected to a different network. Try connecting over UART and confirm that it is connected to the ASE network using nmtui
  2. The Rover is assigned an incorrect IP address. Try connecting over UART and confirm that the IP address corresponds to the expected IP using ifconfig. If the IP does not match, ask an ASE team member (the DHCP server might be misconfigured or the Rover needs to be reflashed).

Confirm Connectivity​

If the host is up, use SSH to connect to the Rover. If you cannot connect over SSH this means that the Linux installation might have failed and your Rover needs to be reflashed. Ask an ASE team member for help.

Confirm roverd is Operational​

If you are SSH'ed into the Rover, confirm that roverd is operational by viewing its status first. Then, view its logs for clues. It is always safe to update roverd to the latest version.

After updating, try to query roverd information through roverctl.

roverctl hangs when issuing a command​

Cause​

This most likely means that the roverd API cannot be reached (in time). Follow these trouble shooting steps.

roverctl fails with connection refused​

Cause​

This means that the roverd API is not reachable or not operational. Follow these trouble shooting steps.

roverctl fails with address not available​

Cause​

This means that the you are not connected to the ASE network. Read how to connect.

roverctl-web fails to resolve the Rover's hostname​

Cause​

Your browser fails to resolve the hostname of a Rover over mDNS

Sanity Checks​

  • Is the Rover powered on and does its display show its name and index?
  • Did you specify the correct Rover index?
  • Are you connected to the ASE network?
  • Is the network experiencing high load?

Trouble Shooting​

Try to resolve the Rover's IP manually using ping:

# Try to resolve the address of Rover 7
ping rover07.local

# Expected output: (IPs may differ)
64 bytes from 192.168.0.107: icmp_seq=0 ttl=64 time=64.046 ms
64 bytes from 192.168.0.107: icmp_seq=1 ttl=64 time=4.771 ms

Then, start roverctl-web with the custom host you discovered:

# Use --host instead of --rover
roverctl --host 192.168.0.107