Avatar of Jason B
Jason B
Flag for United States of America asked on

Server not responding vSphere Mobile Watchlist

I have three vCenter clusters setup in vSphere. The way I have configured access via web browser is to use load balancers to send client request connections from vsphere.domain.com to any of the three vcenters. There's no priority on which real server gets the client request. Source IP Persistence (stickiness) is set to 1 hour and the load balancers are configured to redirect to port 9443 from 80. This all has worked well both on our local network as well as outside our local network using a web browser. Now we're trying to use the Android vSphere Mobile Watchlist app to access and manage vSphere. On our network if I use the real server IP addresses bypassing my load balancer setup the android app works however, when using the FQDN (vsphere.domain.com) I immediately get "server not responding". What could the app be requesting or using that I need to account for? Different port or protocol? Thank you in advance for any information.
VMwareAndroidVirtualization

Avatar of undefined
Last Comment
Jason B

8/22/2022 - Mon
Abhilash

Is this FQDN publicly resolvable? May be its happening because the watchlist can talk only to VMware environment directly and cannot identify a load balancer.
ASKER CERTIFIED SOLUTION
Jason B

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Jason B

ASKER
I troubleshot and found the issue and the solution.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23