Testing the connection from your Private Scan Hub to AppCheck

Communication between the private scan hub and AppCheck's servers is sensitive to many forms of interception.  AppCheck provides a diagnostics tool to detect problems with the connectivity.  If a problem is detected, the first step is to ensure you have allowed the full range of outbound access described in Private Scan Hub Requirements - VM Network Access, including bypassing any systems that might inspect or modify packets.

Hubs running the latest version of our scan hub software can view the output of this tool in the Diagnostics tab of their scan hub's local web interface:

For users who cannot upgrade their hub to the latest version (for example when connectivity issues are preventing the hub from provisioning or updating), the tool can be manually downloaded and run from the hub's Command Line Interface (CLI). To download and use the tool, log in to the hub's CLI and execute the following commands:

sudo apt update && sudo apt install scanhub-diagnostics

Once installed, run the tool using the following command:

sudo scanhub-diagnostics

The last few lines of the tool ouput include a timestamp, and confirmation of whether the tests completed successfully or not.  The following shows a successful result:

If passed does not equal true then there is a problem with the connectivity, which will be detailed further up in the output.  If the output does not make it clear to you what is causing the problem, you may wish to raise a ticket with AppCheck Support and share the output with them.