Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
When using Test Connection on the Workspace ONE UEM Console, you receive a 'Test is unsuccessful' error message.
During the SEG test connection, six checks are performed: Test Connection result from Airwatch(or Web) to SEG This check ensures the SEG is accessible from outside the network. While these checks are performed from the AirWatch Console server, they must be valid for all devices connecting to the SEG. Hostname found - This check confirms that the external hostname specified for the SEG server is resolved to an IP address. A simple variation of this test is to use the command prompt from a computer outside the domain to issue a command and confirm the hostname resolves correctly. If the test connection is failing at this step, make sure that the SEG Server is accessible from the public network.SEG SSL certificate trusted - This check confirms the SSL certificate bound to the SEG server is properly configured. Some common reasons for an occurrence of failure include: The SSL certificate has expiredThe SSL certificate does not have proper root/intermediate certificates installed on the serverThe SSL certificate was issued to a different hostname other than what is specified in the configurationThe CRL of the SEG certificate is not publicly available If Test Connection is failing at this step, replace the SEG certificate with a proper SSL certificate following this article. Connectivity from Airwatch to SEG - If the test connection is failing at this step, try to access https://SEG_URL from any machine in public network. We expect an 'OK' message on the browser when SEG page opens up. Test Connection result from Airwatch(or Web) to SEG This check ensures the AirWatch API server is accessible from the SEG server. When confirming these checks, all tests should be performed from the SEG server itself. Hostname found - This check confirms the hostname specified for the AirWatch API server is resolved to an IP address. If test connection fails at this step, make sure that API Server is reachable from the SEG server on port 443.AW API SSL certificate trusted - This check ensures the SSL certificate bound to the API server is properly configured. Some common reasons for this to fail are: The SSL certificate of API Server has expiredThe SSL certificate does not have proper root/intermediate certificates installed on the serverThe SSL certificate was issued to a different hostname other than what is specified in the configurationThe CRL of the API server’s certificate is not accessible from the SEG serverA handshake error has occurred due to incompatible protocols or cipher suites between the API and SEG servers Connectivity from SEG to Airwatch - This ensures a proper connection can be established between the SEG and AirWatch API. This should be good if the above two checks have passed. If the issue still persists after performing these troubleshooting steps, raise a request with VMware Support to troubleshoot the issue further.