Published Vmware vSphere on MAB Web portal.

[Sergey_Anikeev]

Hello colleagues!

Please tell me what direction to look in if anyone has encountered a similar problem.

We have a Vmware vSphere server deployed on a local network, and we want to publish web access to it from the outside through the Mobile Access Web portal.

To do this, we have created a custom Web Application and published it on the MAB portal.

However, after successful login, the connection does not proceed further, no progress after login and no error or blocks.

[emmap]

I see you've allowed ports 80 and 443, I haven't used VMWare in a while but I remember needing more ports than just 443 to log in to ESX. Do you see any other ports being dropped in your logs, or can you check VMWare documentation to see if there's more that need adding?

[Sergey_Anikeev]

It looks like only port 443 is being used.
We don't see any other port requests in the logs.

[Vincent_Bacher]

Our vCenter is behind a firewall, and I just took a look at the logs. If I'm not mistaken with the many logs, I can already see access to 902/udp after logging in, but I'm not entirely sure with the many accesses to the vCenter page.

Maybe take a look here

https://knowledge.broadcom.com/external/article/326184/tcp-and-udp-ports-required-to-accessvmwa.html

edith says: It seems that 902/udp and other ports are used once console is accessed and same for other ports. Just opening the WebUI seems to use 443/tcp only. 

[Sergey_Anikeev]

As far as I understand 902 UDP is a port used in VMware vSphere for communication between platform components.
It is used in the operation of the vCenter server and ESXi hosts.

Only port 443 is used to access the client's Web portal.

P.S.

In addition, UDP ports cannot be added to the list of allowed ports in the Web Application object.
The gateway itself has unrestricted access to the target server via all ports.