Your Traveler server or URL is up and running as expected, there are no reported issues by end-users, and the "Test Connection" from the scanning configuration wizard is successful, yet GSX Monitor still displays a HTTP secure channel link error message.
This article details how to fix this problem.
Symptoms
- Successful connection using the wizard "Test Connection" button.
AND
- HTTP error #10: An error occurred in a secure channel link.
How to Solve the Issue
To solve this problem, we need to force GSX Monitor to use Secure Sockets Layer version 3 (SSLv3) rather than the default TLS 1.0 as the connection securing method.
To force GSX Monitor to use SSLv3:
- Stop GSX Monitor including all background processes.
- Locate the GSX Monitor\Data\GSXScanEngine.ini file.
- Open GSXScanEngine.ini using a text editor.
- Locate the [OPTIONS] section.
- Set the URLOPTIONS to use SSLv3: URLOPTIONS=SSL3=TRUE.
- Save your modifications to GSXScanEngine.ini.
- Launch GSX Monitor as an Application for modifications to be taken into account.
The issue was occurring because GSX Monitor was no longer allowed to connect to the scanned resource using the default connection securing method. There may have been a security update performed at the server level that is now preventing TLS 1.0 secured connections for example.
Scanning process and protocols:
- URL Scanning: TLS 1.0 or SSLv3
- Notes Traveler Server Scanning: TLS 1.0 or SSLv3
- Notes Traveler Pool URL Scanning: SSLv3 only