Common issues: Node to CycleCloud connectivity

CycleCloud installs an agent on each virtual machine that needs to communicate with the CycleCloud application. The agent reports status and monitoring data and makes API requests for autoscaling and distributed synchronization.

We recommend deploying the application server in the same virtual network as the cluster. If you can't use this configuration, establish connectivity by doing virtual network peering or using a proxy node. These error messages indicate that nodes can't communicate with the CycleCloud application server.

Possible error messages

• Timeout awaiting system boot-up
• Timed out connecting to CycleCloud at {https://A.B.C.D}
• Connection refused to CycleCloud through return-proxy tunnel at {https://A.B.C.D:37140}
• Unable to setup return proxy: cannot connect to {A.B.C.D:22}
• Could not connect to
• Certificate validation failed for CycleCloud

Resolution

• If the CycleCloud server and the cluster are in the same virtual network, check the network security groups for the subnets in the virtual network. Cluster nodes need to reach the CycleCloud server at TCP 9443 and 5672. In the other direction, Azure CycleCloud needs to reach ganglia (TCP 8652) and SSH (TCP 22) ports of the cluster for system and job monitoring.

• Add a public IP address.

• Check the return proxy settings if the error message indicates a return proxy.

• After updating network or proxy settings, test connectivity by SSHing into the node as the cyclecloud user and using curl -k {https://error-message-url}.

• After validating that network connectivity is fixed, terminate and restart the node.

More information

Learn more about network connectivity. Learn more about return proxy.