On June 13, we deployed a new security certificate to our servers — a routine update that ensures secure communication between our product and our cloud services. The new certificate was issued by a new Root Certificate Authority (RootCA). This RootCA is part of the trust chain that allows secure connections between our product and our servers.Since then, we have observed that some hub uploads are not being processed as expected.
The issue is related to certain systems not trusting the new certificate, as the internal Microsoft certificate store may not update automatically. This can cause uploads to fail with an error such as:
VDog HubUpload.exe failed. [Exit code: 4294967295] [Details: Hub connection - SSL peer certificate or SSH remote key was not OK (CURL error code: 60)] [Error code: 42210]
Recommended Solutions (try in this order):
Important:If your company uses an SSL inspection firewall, please ensure that the RootCA is set as trusted within the firewall configuration. Otherwise, SSL connections may be blocked or altered, leading to validation errors.
Note:This issue may also affect automatic usage data uploads. Manual uploads via Microsoft Edge or other third-party browsers should still work, as these use separate certificate stores.
We apologize for any inconvenience.