Category: VCSA

Could not connect to VCSA port 7331

When rebuilding my lab and installing VCSA 5.5, I notes that after a reboot of the VCSA I could no longer connect to my VM’s via the web clients console. I just got a webpage saying; Could not connect to VCSA_Address:7331. As I’m using the VCSA in my lab and with my clients I was a bit disappointed. VMWare has the KB2060604 that solves this problem, but I think that the “fix” should be in all my VCSA setups and therefor this post. Maybe VMware should insert the one line, “set.default.VMWARE_JAVA_HOME=/usr/java/jre-vmware” into the wrapper.conf found in the folder/usr/lib/vmware-vsphere-client/server/wrapper/conf, by default? so this issue not occurs if the VMWARE_JAVA_HOME environmental variable is not properly set after restarting the vCenter Server Appliance. Hobe this will help you as well, please leave a comment below.

Failed to connect to VMware Lookup Service SSL certificate verification failed.

When installing the VCSA on a network with DHCP your VCSA will get an IP from the DHCP as it’s configured to use DHCP out-of-the-box. This however will give you some trouble down the road. If you start the confingur the VCSA with the DHCP IP you will get an error when trying to connect to the vSphere Web Client. Something like: Failed to connect to VMware Lookup Service https://:7444/lookupservice/sdk – SSL certificate verification failed. The VMware KB artikel 2033338 suggest that changing the certificate will do the trick. But I found that when you install the VCSA and boot it for the first time, disconnect the network will resulting in not IP for the VCSA 🙂 Then you can change the DHCP default to a static IP by logging in to the appliance (default user root and password vmware) and using /opt/vmware/share/vami/vami_config_net command to configuer the IP. After setting the static IP, Gateway ect. connect the VCSA to the network again. You can now go the http://your-vcsa-ip:5480 and start the config wizard and your vSphere web client will work!