Unexpected exception during gather of site BES Support: Unexpected HTTP response: 404 Not Found

Dear All,

I hope you are doing well.

Kindly advise regarding a new HCL BigFix version 11.0.6 installation.

The installation completed successfully. During the licence authorisation step, I configured the proxy successfully, and the activation completed without any issues.

After the installation, I waited for BigFix to synchronise the sites; however, no sites have been synchronised, as the BigFix management domain is not shown, so I am unable to enable any external sites.

I have verified the following:

The Gather service is running correctly.

The following local URL is accessible:

http://127.0.0.1:52311/cgi-bin/bfenterprise/BESGatherMirrorNew.exe

Both of the following URLs are reachable from the BigFix server:

https://gatherer.bigfix.com

http://gatherer.bigfix.com

Curl connectivity tests were also completed successfully.

Verifying BigFix license server connectivity (http://gatherer.bigfix.com/cgi-bin/LicenseServerFrontend.pl)

However, after reviewing the GatherDB.log, I found the following error:

Unexpected exception during gather of site BES Support: Unexpected HTTP response: 404 Not Found

Could you please advise what could be causing this issue?

For your reference, I have attached the following:

GatherDB.log:

Sun, 19 Jul 2026 16:50:18 +0300 -- GatherDB version 11.0.6.137 starting...
Sun, 19 Jul 2026 16:50:18 +0300 -- Using cURL library - 8.18.0
Sun, 19 Jul 2026 16:50:18 +0300 -- OpenSSL Initialized (Non-FIPS Mode)
Sun, 19 Jul 2026 16:50:18 +0300 -- Using OpenSSL crypto library OpenSSL 3.5.5 27 Jan 2026
Sun, 19 Jul 2026 16:52:22 +0300 -- Unexpected exception during gather of site BES Support: Unexpected HTTP response: 404 Not Found
Sun, 19 Jul 2026 16:56:28 +0300 -- Unexpected exception during gather of site BES Support: Unexpected HTTP response: 404 Not Found
Sun, 19 Jul 2026 17:01:17 +0300 -- GatherDB Stop Requested.
Sun, 19 Jul 2026 17:01:18 +0300 -- GatherDB version 11.0.6.137 starting...
Sun, 19 Jul 2026 17:01:18 +0300 -- Using cURL library - 8.18.0
Sun, 19 Jul 2026 17:01:18 +0300 -- OpenSSL Initialized (Non-FIPS Mode)
Sun, 19 Jul 2026 17:01:18 +0300 -- Using OpenSSL crypto library OpenSSL 3.5.5 27 Jan 2026
Sun, 19 Jul 2026 17:03:21 +0300 -- Unexpected exception during gather of site BES Support: Unexpected HTTP response: 404 Not Found
Sun, 19 Jul 2026 17:05:26 +0300 -- GatherDB Stop Requested.
Sun, 19 Jul 2026 17:05:27 +0300 -- GatherDB version 11.0.6.137 starting...
Sun, 19 Jul 2026 17:05:27 +0300 -- Using cURL library - 8.18.0
Sun, 19 Jul 2026 17:05:27 +0300 -- OpenSSL Initialized (Non-FIPS Mode)
Sun, 19 Jul 2026 17:05:27 +0300 -- Using OpenSSL crypto library OpenSSL 3.5.5 27 Jan 2026
Sun, 19 Jul 2026 17:07:31 +0300 -- Unexpected exception during gather of site BES Support: Unexpected HTTP response: 404 Not Found

BESRelay.log:

Sun, 19 Jul 2026 16:50:19 +0300 - Main Thread (2528) - BES Root Server version 11.0.6.137 built for WINVER 10.0 x86_64 running on WINVER 10.0.20348 i386, starting
Sun, 19 Jul 2026 16:50:19 +0300 - Main Thread (2528) - Using cURL library - 8.18.0
Sun, 19 Jul 2026 16:50:19 +0300 - Main Thread (2528) - OpenSSL Initialized (Non-FIPS Mode)
Sun, 19 Jul 2026 16:50:19 +0300 - Main Thread (2528) - Using OpenSSL crypto library OpenSSL 3.5.5 27 Jan 2026
Sun, 19 Jul 2026 16:50:19 +0300 - Main Thread (2528) - Successfully connected to database
Sun, 19 Jul 2026 16:50:19 +0300 - Main Thread (2528) - Signature Algorithms: sha384, sha256
Sun, 19 Jul 2026 16:50:19 +0300 - Main Thread (2528) - Download Algorithms: sha256, sha1
Sun, 19 Jul 2026 16:50:19 +0300 - Main Thread (2528) - TLS Cipher List: HIGH:!ADH:!AECDH:!kDH:!kECDH:!kRSA:!PSK:!SRP:!SHA1
Sun, 19 Jul 2026 16:50:19 +0300 - Main Thread (2528) - Successfully read server signing key
Sun, 19 Jul 2026 16:50:19 +0300 - Main Thread (2528) - Successfully read client CA key
Sun, 19 Jul 2026 16:50:27 +0300 - LicenseUpdater (3132) - HTTP gather for http://gatherer.bigfix.com/cgi-bin/LicenseServerFrontend.pl was successful. HTTPS connection to {https://gatherer.bigfix.com/cgi-bin/LicenseServerFrontend.pl} was unsuccessful due to {HTTP Error 60: SSL peer certificate or SSH remote key was not OK: SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)}; retried using HTTP
Sun, 19 Jul 2026 16:51:59 +0300 - /cgi-bin/bfenterprise/clientregister.exe (6132) - The re-registration request for ComputerID 1075533534 failed. Request details: SequenceNumber=8, ProxyDevice=false, MacAddressList=00-50-56-89-7e-23_00-50-56-89-fa-a0, RegistrationIPAddress=10.10.150.192
Sun, 19 Jul 2026 16:52:22 +0300 - 6884 - HTTP gather for http://sync.bigfix.com/cgi-bin/bfgather/bessupport?Time=1784469140 was successful. HTTPS connection to {https://sync.bigfix.com/cgi-bin/bfgather/bessupport?Time=1784469140} was unsuccessful due to {HTTP Error 60: SSL peer certificate or SSH remote key was not OK: SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)}; retried using HTTP
Sun, 19 Jul 2026 16:54:21 +0300 - /api/webui-sites (4964) - Unable to find site id for URL: http://sync.bigfix.com/cgi-bin/bfgather/webui-common
Sun, 19 Jul 2026 16:54:25 +0300 - 8976 - HTTP gather for http://sync.bigfix.com/cgi-bin/bfgather/webui-common?Time=1784469263 was successful. HTTPS connection to {https://sync.bigfix.com/cgi-bin/bfgather/webui-common?Time=1784469263} was unsuccessful due to {HTTP Error 60: SSL peer certificate or SSH remote key was not OK: SSL certificate OpenSSL verify result: self-signed certificate in certificate chain (19)}; retried using HTTP

You are using HTTPS proxy, you can see that all of your HTTPS request are failing and fallback to HTTP.

If you want to allow HTTPS comm - add the PROXY certificates to the bundle - Customizing HTTPS for Gathering

See also additional KB - BigFix SSL Certificate issues with Secure Proxy - Customer Support

1 Like

Hi Orbiton,

Thanks for your support and cooperation

Will double-check with security team, as they tested from browser on the BigFix server, and it works fine even HTTP or HTTPS

The browser is using a different trusted certificate store then the Application , I suggest you to configure as the documentation says and update the results

Thanks orbiton will discuss this with them