Aria Operations Cloud Proxy Connection Issue
- Mohammed Bilal
- Jul 8
- 1 min read
I recently encountered an issue while deploying the Cloud Proxy for Aria Operations, where the proxy failed to establish a connection with the Aria Operations node.
The Cloud Proxy was deployed to monitor my vCenter environment in order to enable configuration drift detection in vROps.
Despite reviewing the error details "Failed to connect to VMware Aria Operations after 30 retries", I was unable to find any relevant information explaining why the Cloud Proxy was unable to join the Aria Operations nodes.

Reconfirmed that the provided OTK from the Aria Ops page is correct.
As part of the initial troubleshooting steps, I verified the network connectivity between the Cloud Proxy appliance and the Aria Operations node, and the ping test was successful.

Verified the deployment status from the command line using the command: cprc-cli -s.

Conducted further debugging on the Cloud Proxy using the command cprc-cli -d all, but it did not reveal any issues.

I discussed the issue internally with colleagues and was informed that a Load Balancer IP must be configured even for a single-node vROps deployment. In such cases, the IP of the single node itself should be used as the "Load Balancer IP."
Upon reviewing the deployment parameters, I confirmed that I had not specified the Load Balancer IP, as I assumed it wasn't required for a single-node setup.

I deleted and re-deployed the Cloud Proxy appliance, this time specifying the single-node Aria Operations IP as the Load Balancer IP. As a result, the Cloud Proxy successfully connected to the Aria Operations node.


Following this, I successfully created the configuration drift template.
