Skip to main content

Troubleshooting

Start with the controller, then verify the local agent state.

Device does not appear connected​

Check:

  • The agent is installed and running.
  • The device identity shown by the local UI or netsody status matches the device in the controller.
  • The device is assigned to the expected network.
  • The device has network connectivity to the controller.

Devices cannot reach each other​

Check:

  • Both devices are connected to the same Netsody network.
  • A policy allows communication between their groups.
  • Their Netsody IP addresses are in the expected network range.
  • No local firewall blocks the traffic on either device.
  • The Netsody subnet does not overlap with a local LAN subnet.

Resource is unreachable​

Check:

  • The gateway device is online.
  • The gateway can reach the target subnet locally.
  • Linux IP forwarding and NAT are enabled on the gateway.
  • A resource exists for the destination.
  • Access to the resource is allowed for the source group.

Local diagnostics​

Use netsody status to inspect the local agent state and retrieve the device public key.

On desktop systems, the local Netsody UI can also show whether the agent is connected and which networks are active.

Support​

If the issue persists, contact the Netsody team through: