Hello,
I read a lot of article regarding this issue, but I didnt made it.
Szenario:
Site 1 -> vCenter Server with Update Manager -> Internet -> Site 2 -> Router/DNAT (port forwarding 8081 -> 443) -> ESXi-Host
(furthermore 902/903/5898/TCP/UDP are unchanged forwarded @ site 2 to the host)
When I try to add the host to vCenter server it will start to add it and breaks @ 80% of adding with communication failure. I guess there is a point while adding the host where vCenter server again uses port 443 instead of 8081 because of vCenter server reads the config direc from the host and sees port 443 configured ther. So until the communication breaks I see the ssl fingerpint, the vms, the license, etc.
When vCenter accesses the ESXi system with port 443 all will be fine, updates also. But port 443 is used for an other app @ site 2, so I need to access the ESXi host by another port.
Direct access via vSphere client -> ESXi host is no problem, even when we use port 8081 forwarded to port 443.
We changes the setting in reversehttp-proxy config.xml and in proxy.xml - nothin happens. rproxyhttpd still listens on 443.
Is this a bug, that rproxyhttpd doesnt use the information from the config file? Does anybody knows how to configure this right?
Best regards
Jan