Summary: VxRail plugin is not working however the legacy GUI is accessible normally after enabling it from runtime.properties
Article Content
Issue | For a VxRail cluster using external vCenter, the VxRail plugin is giving an error which is "The VxRail manager server may be unreachable, please check and try again later." however the legacy GUI is working normally. To identify this issue, SSH to vCenter and check the following file /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log We will find errors like: [2020-04-12T09:03:54.210+02:00] [ERROR] p-nio-127.0.0.1-5090-exec-62 com.vmware.vxrail.mvc.ServiceProxyController Error occurred when calling VxRail Manager REST API org.apache.http.conn.HttpHostConnectException: Connect to 10.137.64.191:443 [/10.137.64.191] failed: Connection timed out (Connection timed out) Caused by: java.net.ConnectException: Connection timed out (Connection timed out) at java.net.PlainSocketImpl.socketConnect(Native Method) |
Cause | This issue is caused when ports 443 and 80 are closed from the vCenter side to VxRail side and these two ports need to be opened both ways from VxRail manager to vCenter and vice versa. To double check the status of the ports SSH to vCenter IP and run the following command: $ curl -v telnet://<VxRail_IP>:port You would need to replace <VxRail_IP> with your current IP and the port to 80 one time and 443 another time- If the curl command worked, it will give a connected state which means that the port is opened. - If the curl command didn't work, it will give a failed message which means that the port is closed. |
Resolution | Open both ports 443 and 80 between vCenter and VxRail and vice versa then check again the plugin. |