Skip to main content

Connectivity Troubleshooting

If your Awetobot is unable to connect to Awetonet.io, the most common cause is a firewall or network policy blocking outbound traffic.

You can test connectivity directly from the Awetobot terminal using nc (Netcat).

Run all connectivity tests​

Copy and paste the following commands into the Awetobot terminal:

nc -vz bot.awetonet.io 22
nc -vz bot.awetonet.io 443
nc -vz nms.awetonet.io 5669
nc -vz nms.awetonet.io 5556
nc -vzu vpn.awetonet.io 1194

Expected results​

For the TCP tests, a successful connection should return a message similar to:

Connection to bot.awetonet.io 22 port [tcp/ssh] succeeded!
Connection to bot.awetonet.io 443 port [tcp/https] succeeded!
Connection to nms.awetonet.io 5669 port [tcp/*] succeeded!
Connection to nms.awetonet.io 5556 port [tcp/*] succeeded!

The exact wording may vary depending on the version of nc installed on your Awetobot.

note

UDP connectivity cannot be confirmed using nc alone​

UDP is connectionless and does not establish a connection in the same way as TCP.

The following command can be used as an initial test:

nc -vzu vpn.awetonet.io 1194

However, a successful response from nc does not definitively confirm that UDP traffic is reaching the VPN service.

The VPN connection itself is the definitive test for UDP/1194 connectivity.

Required outbound access​

The firewall must allow the following outbound connections from the Awetobot:

DestinationProtocolPortPurpose
bot.awetonet.ioTCP22Awetobot SSH
bot.awetonet.ioTCP443Awetobot HTTPS
nms.awetonet.ioTCP5669NMS connectivity
nms.awetonet.ioTCP5556NMS connectivity
vpn.awetonet.ioUDP1194VPN connectivity
info

These connections are outbound from the Awetobot. No inbound firewall rule is required for the Awetobot to establish these connections.

If a TCP test fails​

A failed TCP test may return an error such as:

  • Connection timed out — traffic is likely being dropped somewhere along the network path, commonly by a firewall or network security policy.
  • Connection refused — the destination was reachable, but the connection was rejected.

The exact error message may vary depending on the network and firewall configuration.

If a TCP test fails, check that outbound traffic to the required destination and port is permitted.

Connection timed out​

A timeout usually indicates that traffic is being dropped somewhere along the network path, commonly by a firewall or network security policy.

Check that outbound traffic to the required destination and port is permitted.

Connection refused​

A connection refused response means the destination was reachable, but the connection was rejected.

If you receive this response for an Awetonet.io service, contact Awetonet.io Support and provide the command output.

Firewall checklist​

If any of the TCP tests fail, check the following:

  • Outbound traffic is permitted from the Awetobot.
  • TCP 22 to bot.awetonet.io is permitted.
  • TCP 443 to bot.awetonet.io is permitted.
  • TCP 5669 to nms.awetonet.io is permitted.
  • TCP 5556 to nms.awetonet.io is permitted.
  • UDP 1194 to vpn.awetonet.io is permitted.
  • No higher-priority firewall rule is blocking the traffic.
  • No application-control, web-filtering, or network-security policy is overriding the outbound rule.
tip

If your firewall uses a default deny outbound policy, these destinations and ports must be explicitly allowed.

Need help?​

If connectivity is still unavailable after allowing the required outbound traffic, send Awetonet.io Support:

  1. The output from all five nc commands.
  2. The firewall rule allowing the outbound traffic.
  3. The firewall vendor and model.
  4. The network location where the Awetobot is installed.

This information will help us identify where the connection is being blocked.