This problem only started happening since I upgraded my vRO external cluster from 7.2 to 7.4.
I have been having a lot of problems ever since the upgrade with vRO.
1st node was upgraded from 7.2 to 7.4
2nd node is a newly deployed vRO 7.4 appliance, which took on the same IP address and Hostname or old 2nd, and was added to the cluster (followed the upgrade procedure provided by VMware)
If I set both my vRO nodes as active in the LB, then I get an error in VRA's VRO server configuration saying "unable to connect to port", however when I set the weight or disable the 2nd node I get a successful connection.
Nothing in vRO control center or in logs was indicating that there is something wrong with the cluster, but after I removed the 2nd node from the cluster it resolved my external Orchestrator server connection as well as the timeouts I was getting when trying to deploy blueprints.