N-central Troubleshooting
VMWare Connectivity service fails with the following error: Unable to establish CIM session with ESX server: The remote server returned an error: (502) Bad Gateway
Last Modified
Tue Dec 01 22:11 GMT 2020
Description
- VMWare Connectivity service fails with the following error: Unable to establish CIM session with ESX server: The remote server returned an error: (502) Bad Gateway
- This article explains what to do if the VMWare Connectivity service returns the following error:
- Unable to establish CIM session with ESX server: The remote server returned an error: (502) Bad Gateway.
Environment
- N-able N-central
Solution
- The error "(502) Bad Gateway" indicates there is either a routing issue or a proxy issue between the Probe and the VMWare ESX/ESXi server.
- Please do the following to resolve:
- Check the network settings for both the Probe and the VMWare ESX/ESXi servers, ensuring the Subnet Mask is correct and the correct Gateway is configured.
- Check the System Proxy settings on the Probe (The can be done from Internet Explorer's Settings).
- NOTE: If there is a proxy in place, and the VMWare server is on the same subnet, enable the option to bypass it for local addresses, or whitelist the VMWare ESX/ESXi server address in the proxy.