Important Notice: 
SSL Certificate Update May Affect Hub Uploads and Usage Data Automation

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):

  1. Open the following URL in the Edge browser on the octoplant server:
    👉 https://api.amdt.io/
    (This typically triggers a certificate update in the system certificate store.)
  2. Manual certificate import (if step 1 does not resolve the issue):
    • Open https://api.amdt.io/ in Microsoft Edge.
    • Click the lock icon in the address bar and open the certificate details.
    • In the Details tab, select the root certificate “Sectigo Public Server Authentication Root R46” and click Export.
    • Copy the exported certificate to the affected octoplant server.
    • Double-click the file and choose Local Machine as target.
    • Select Trusted Root Certification Authorities as the destination store and complete the wizard.
  3. As a fallback, use PowerShell on the octoplant server to run:
    (Navigate to your installation folder, typically C:\Program Files (x86)\vdogServer\auvesy_services)

    .\curl.exe -v https://upload-hub.octoplant.com/ --ca-native
     

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.