systemctl status proton" shows "active (running)", but the UI and API never become reachable.VCF 9.1.1
VMware NSX 9.1.1 and above
During startup, NSX Manager runs a validation step for host-based agent VM services deployed through VMware ESX Agent Manager (EAM). In some environments this step doesn't complete, and the startup waits indefinitely.
This is a known issue impacting VMware NSX. Subscribe to this KB article to be updated if a fix version becomes available.
The workaround needs to be applied to every NSX Manager node in the cluster, one node at a time.
cp /usr/tanuki/conf/proton-tomcat-wrapper.conf /root/proton-tomcat-wrapper.conf.bak-$(date +%s)/usr/tanuki/conf/proton-tomcat-wrapper.conf for editing:vi /usr/tanuki/conf/proton-tomcat-wrapper.confwrapper.java.additional.<N>=" line and note its number (for example, .69).wrapper.java.additional.70=-Dsun.net.client.defaultConnectTimeout=20000wrapper.java.additional.71=-Dsun.net.client.defaultReadTimeout=120000systemctl restart protonsystemctl status proton" and confirm it shows "active (running)" and the UI and API are reachable.