Backup Agent Issue

Bare Metal and VPS
1

Hello,

I've a bare metal server and I tried to configure the Backup Agent on a Linux VM (VMWare is running bare metal).

I follow the istructions here https://docs.ovhcloud.com/en/guides/storage-and-backup/backup-agent/first-configuration, but when I launch:

~$ sudo veeamconsoleconfig -s
Management agent
    Connection state       : Disconnected (Failed to connect to the specified cloud gateways)
Backup agent
    Status                 : Not installed

...and I don't see the agent running in the web console. How can I proceed?

Best

Francesco

2

Hi @mitsus,

I assume you have added the server to your backup agent, but after that you need to install the agent on the server (I think you don’t have it installed and that’s why it shows Status: not installed)

Once installed, check that your firewall is not blocking the communication:

telnet vspc-cgw1.prod01.eu-west-rbx.backup.ovh.net 6180

If the command fails, the firewall is blocking the connection.

On Linux, you can open the outbound port temporarily with:

iptables -I OUTPUT -d <direccion_del_gateway> -p tcp --dport 6180 -j ACCEPT

Let us know, cheers.
Sergio Turpín

3

Hi @sturpin ,

thanks for your reply.

$ telnet vspc-cgw1.prod01.eu-west-rbx.backup.ovh.net 6180
Server lookup failure:  vspc-cgw1.prod01.eu-west-rbx.backup.ovh.net:6180, Name or service not known

It doesn't resolve this name, but the others do. I also tried opening the outbound firewall port, but the error is still the same.

4

Hi @mitsus

I only put that as an example; in the confirmation email for your Backup Agent order you received the exact connection information you should use.

Let me know, best regards.
Sergio Turpín

5

Hi @sturpin,

the assigned server is:

Cloud gateways (assigned) : ``vspc-cgw51.prod01.eu-west-rbx.backup.ovhcloud.com:6180

trying to reach it works fine:

$ telnet ``vspc-cgw51.prod01.eu-west-rbx.backup.ovhcloud.com`` 618
Trying 145.239.193.234...
Connected to ``vspc-cgw51.prod01.eu-west-rbx.backup.ovhcloud.com``.
Escape character is '^]'.

The problem is somewhere else. Could you help me debug?

6

Hi @mitsus

  1. You need to reconfigure the management agent with the correct address:
    sudo veeamconsoleconfig -g add vspc-cgw51.prod01.eu-west-rbx.backup.ovhcloud.com:6180
  2. Restart the service:
    sudo veeamconsoleconfig --restart_service
  3. Check the status again:
    sudo veeamconsoleconfig -s

If everything went well, the Connection state field should appear as Connected.

If after these steps the state remains Disconnected, I recommend reviewing the agent logs. You can find them in the agent’s installation directory, usually under /var/log/veeam/ or a similar path. There you’ll see more specific error messages that can help you pinpoint the issue.

Let us know how it goes. Regards.
Sergio Turpín

7

Hi @sturpin,

same problem again.

Analyzing the logs in /var/log/veeam/veeaminstaller.log, on restart with sudo veeamconsoleconfig --restart_service I only see this:

[28.07.2026 21:09:37.808] <134949979753344> installer| Command line: [/var/lib/veeamma/utils/x64/veeaminstaller, --system-info, VAC]
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon| File [/etc/veeam/veeam.ini] does not exist, default settings will be used.
[28.07.2026 21:09:37.809] <134949979753344>          | LOG: Initializing log file for process with PID 2381003
[28.07.2026 21:09:37.809] <134949979753344>          | ====================================================================================
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon| {
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|   Veeam Agent for Linux: /var/lib/veeamma/utils/x64/veeaminstaller.
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|   PID: 2381003
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|   Version: 13.0.1.94
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|   Build edition: standard
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|   Build date: 29/10/2025
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|   hostname: backend-public-services
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|   uname
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     sysname : Linux
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     release : 6.8.0-106-generic
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     version : #106-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar  6 07:58:08 UTC 2026
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     machine : x86_64
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|   cpuinfo
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     processor    : 0
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     model name   : Intel(R) Xeon(R) D-2141I CPU @ 2.20GHz
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     processor    : 1
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     model name   : Intel(R) Xeon(R) D-2141I CPU @ 2.20GHz
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     processor    : 2
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     model name   : Intel(R) Xeon(R) D-2141I CPU @ 2.20GHz
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     processor    : 3
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     model name   : Intel(R) Xeon(R) D-2141I CPU @ 2.20GHz
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     processor    : 4
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     model name   : Intel(R) Xeon(R) D-2141I CPU @ 2.20GHz
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     processor    : 5
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     model name   : Intel(R) Xeon(R) D-2141I CPU @ 2.20GHz
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|   meminfo
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     MemTotal:       16375828 kB
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     MemFree:         1763344 kB
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|     MemAvailable:   14378096 kB
[28.07.2026 21:09:37.809] <134949979753344> lpbcommon|   hostIP
[28.07.2026 21:09:37.810] <134949979753344> lpbcommon|     127.0.0.1
[28.07.2026 21:09:37.810] <134949979753344> lpbcommon|     172.16.0.6
[28.07.2026 21:09:37.810] <134949979753344> lpbcommon|     XX.XXX.XX.XXX
[28.07.2026 21:09:37.810] <134949979753344> lpbcommon|     172.17.0.1
[28.07.2026 21:09:37.810] <134949979753344> lpbcommon|     ::1
[28.07.2026 21:09:37.810] <134949979753344> lpbcommon|     fe80::20c:29ff:fe20:9e41
[28.07.2026 21:09:37.810] <134949979753344> lpbcommon|     fe80::250:56ff:fe0b:aec3
[28.07.2026 21:09:37.810] <134949979753344> lpbcommon| }
[28.07.2026 21:09:37.810] <134949979753344> installer| Running command [/var/lib/veeamma/utils/x64/veeaminstaller] with arguments: [{--system-info}, {VAC}].
[28.07.2026 21:09:37.810] <134949979753344> installer| Collecting system info.
[28.07.2026 21:09:37.811] <134949979753344> posix_sys|   Looking for existing agent id in file [/etc/veeamagentid].
[28.07.2026 21:09:37.811] <134949979753344> posix_sys|   Existing agent id was not found in file.
[28.07.2026 21:09:37.811] <134949979753344> posix_sys|   Retrieving BIOS UUID
[28.07.2026 21:09:37.811] <134949979753344>          |   Creating child process: which with arguments: dmidecode
[28.07.2026 21:09:37.812] <134949979753344>          |   Creating child process: /usr/sbin/dmidecode with arguments: -s, system-uuid
[28.07.2026 21:09:37.814] <134949979753344> posix_sys|   Successfully received BIOS UUID using dmidecode
[28.07.2026 21:09:37.814] <134949979753344> posix_sys|   Hardware UUID: {564d552e-4cf8-9081-fa01-6f1502209e41}
[28.07.2026 21:09:37.814] <134949979753344> posix_sys|   Parsing SOsReleaseInfo from file /etc/os-release
[28.07.2026 21:09:37.814] <134949979753344> posix_sys|   /etc/os-release file content:
[28.07.2026 21:09:37.814] <134949979753344> posix_sys|   PRETTY_NAME="Ubuntu 24.04.4 LTS"
[28.07.2026 21:09:37.814] <134949979753344> posix_sys|   NAME="Ubuntu"
[28.07.2026 21:09:37.814] <134949979753344> posix_sys|   VERSION_ID="24.04"
[28.07.2026 21:09:37.814] <134949979753344> posix_sys|   VERSION="24.04.4 LTS (Noble Numbat)"
[28.07.2026 21:09:37.814] <134949979753344> posix_sys|   VERSION_CODENAME=noble
[28.07.2026 21:09:37.814] <134949979753344> posix_sys|   ID=ubuntu
[28.07.2026 21:09:37.814] <134949979753344> posix_sys|   ID_LIKE=debian
[28.07.2026 21:09:37.814] <134949979753344> posix_sys|   HOME_URL="https://www.ubuntu.com/"
[28.07.2026 21:09:37.814> posix_sys|   SUPPORT_URL="https://help.ubuntu.com/"
[28.07.2026 21:09:37.814> posix_sys|   BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
[28.07.2026 21:09:37.814> posix_sys|   PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
[28.07.2026 21:09:37.814> posix_sys|   UBUNTU_CODENAME=noble
[28.07.2026 21:09:37.814> posix_sys|   LOGO=ubuntu-logo
[28.07.2026 21:09:37.814> configpar|   Configuration content is parsed.
[28.07.2026 21:09:37.814> configpar|   Configuration content is parsed. ok.
[28.07.2026 21:09:37.814> installer|   Getting hostname.
[28.07.2026 21:09:37.814>          |     Creating child process: hostname with arguments: 
[28.07.2026 21:09:37.814>          | Thread started.  Role: 'Stdout reader, pid 2381010', thread id: 134949975881408, parent id: 134949979753344.
[28.07.2026 21:09:37.814>          | Thread started.  Role: 'Stderr reader, pid 2381010', thread id: 134949967488704, parent id: 134949979753344.
[28.07.2026 21:09:37.816>          | Thread finished. Role: 'Stderr reader, pid 2381010'.
[28.07.2026 21:09:37.817> installer|       backend-public-services
[28.07.2026 21:09:37.817>          | Thread finished. Role: 'Stdout reader, pid 2381010'.
[28.07.2026 21:09:37.817> installer|   Getting hostname. ok.
[28.07.2026 21:09:37.817> installer|   Getting fgdn.
[28.07.2026 21:09:37.817>          |     Creating child process: hostname with arguments: --fqdn
[28.07.2026 21:09:37.817>          | Thread started.  Role: 'Stdout reader, pid 2381013', thread id: 134949975881408, parent id: 134949979753344.
[28.07.2026 21:09:37.817>          | Thread started.  Role: 'Stderr reader, pid 2381013', thread id: 134949967488704, parent id: 134949979753344.
[28.07.2026 21:09:37.819> installer|       backend-public-services
[28.07.2026 21:09:37.819>          | Thread finished. Role: 'Stdout reader, pid 2381013'.
[28.07.2026 21:09:37.819>          | Thread finished. Role: 'Stderr reader, pid 2381013'.
[28.07.2026 21:09:37.819> installer|   Getting fgdn. ok.
[28.07.2026 21:09:37.819> installer| Collecting system info. ok.
[28.07.2026 21:09:39.444> installer| Command line: [/var/lib/veeamma/utils/x64/veeaminstaller, --system-info, VAC]
[28.07.2026 21:09:39.444> lpbcommon| File [/etc/veeam/veeam.ini] does not exist, default settings will be used.
[28.07.2026 21:09:39.444>          | LOG: Initializing log file for process with PID 2381047
[28.07.2026 21:09:39.444>          | ====================================================================================
[28.07.2026 21:09:39.444> lpbcommon| {
[28.07.2026 21:09:39.444> lpbcommon|   Veeam Agent for Linux: /var/lib/veeamma/utils/x64/veeaminstaller.
[28.07.2026 21:09:39.444> lpbcommon|   PID: 2381047
[28.07.2026 21:09:39.444> lpbcommon|   Version: 13.0.1.94
[28.07.2026 21:09:39.444> lpbcommon|   Build edition: standard
[28.07.2026 21:09:39.444> lpbcommon|   Build date: 29/10/2025
[28.07.2026 21:09:39.444> lpbcommon|   hostname: backend-public-services
[28.07.2026 21:09:39.444> lpbcommon|   uname
[28.07.2026 21:09:39.445> lpbcommon|     sysname : Linux
[28.07.2026 21:09:39.445> lpbcommon|     release : 6.8.0-106-generic
[28.07.2026 21:09:39.445> lpbcommon|     version : #106-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar  6 07:58:08 UTC 2026
[28.07.2026 21:09:39.445> lpbcommon|     machine : x86_64
[28.07.2026 21:09:39.445> lpbcommon|   cpuinfo
[28.07.2026 21:09:39.445> lpbcommon|     processor    : 0
[28.07.2026 21:09:39.445> lpbcommon|     model name   : Intel(R) Xeon(R) D-2141I CPU @ 2.20GHz
[28.07.2026 21:09:39.445> lpbcommon|     processor    : 1
[28.07.2026 21:09:39.445> lpbcommon|     model name   : Intel(R) Xeon(R) D-2141I CPU @ 2.20GHz
[28.07.2026 21:09:39.445> lpbcommon|     processor    : 2
[28.07.2026 21:09:39.445> lpbcommon|     model name   : Intel(R) Xeon(R) D-2141I CPU @ 2.20GHz
[28.07.2026 21:09:39.445> lpbcommon|     processor    : 3
[28.07.2026 21:09:39.445> lpbcommon|     model name   : Intel(R) Xeon(R) D-2141I CPU @ 2.20GHz
[28.07.2026 21:09:39.445> lpbcommon|     processor    : 4
[28.07.2026 21:09:39.445> lpbcommon|     model name   : Intel(R) Xeon(R) D-2141I CPU @ 2.20GHz
[28.07.2026 21:09:39.445> lpbcommon|     processor    : 5
[28.07.2026 21:09:39.445> lpbcommon|     model name   : Intel(R) Xeon(R) D-2141I CPU @ 2.20GHz
[28.07.2026 21:09:39.445> lpbcommon|   meminfo
[28.07.2026 21:09:39.445> lpbcommon|     MemTotal:       16375828 kB
[28.07.2026 21:09:39.445> lpbcommon|     MemFree:         1745716 kB
[28.07.2026 21:09:39.445> lpbcommon|     MemAvailable:   14360480 kB
[28.07.2026 21:09:39.445> lpbcommon|   hostIP
[28.07.2026 21:09:39.445> lpbcommon|     127.0.0.1
[28.07.2026 21:09:39.445> lpbcommon|     172.16.0.6
[28.07.2026 21:09:39.445> lpbcommon|     XX.XXX.XX.XXX
[28.07.2026 21:09:39.445> lpbcommon|     172.17.0.1
[28.07.2026 21:09:39.445> lpbcommon|     ::1
[28.07.2026 21:09:39.445> lpbcommon|     fe8... ...
[28.07.2026 21:09:39.445> lpbcommon| }
[28.07.2026 21:09:39.446> installer| Running command [/var/lib/veeamma/utils/x64/veeaminstaller] with arguments: [{--system-info}, {VAC}].
[28.07.2026 21:09:39.446> installer| Collecting system info.
[28.07.2026 21:09:39.446> posix_sys|   Looking for existing agent id in file [/etc/veeamagentid].
[28.07.2026 21:09:39.446> posix_sys|   Existing agent id was not found in file.
[28.07.2026 21:09:39.446> posix_sys|   Retrieving BIOS UUID
[28.07.2026 21:09:39.446>          |   Creating child process: which with arguments: dmidecode
[28.07.2026 21:09:39.448>          |   Creating child process: /usr/sbin/dmidecode with arguments: -s, system-uuid
[28.07.2026 21:09:39.449> posix_sys|   Successfully received BIOS UUID using dmidecode
[28.07.2026 21:09:39.449> posix_sys|   Hardware UUID: {564d552e-4cf8-9081-fa01-6f1502209e41}
[28.07.2026 21:09:39.449> posix_sys|   Parsing SOsReleaseInfo from file /etc/os-release
[28.07.2026 21:09:39.449> posix_sys|   /etc/os-release file content:
[28.07.2026 21:09:39.449> posix_sys|   PRETTY_NAME="Ubuntu 24.04.4 LTS"
[28.07.2026 21:09:39.449> posix_sys|   NAME="Ubuntu"
[28.07.2026 21:09:39.449> posix_sys|   VERSION_ID="24.04"
[28.07.2026 21:09:39.449> posix_sys|   VERSION="24.04.4 LTS (Noble Numbat)"
[28.07.2026 21:09:39.449> posix_sys|   VERSION_CODENAME=noble
[28.07.2026 21:09:39.449> posix_sys|   ID=ubuntu
[28.07.2026 21:09:39.449> posix_sys|   ID_LIKE=debian
[28.07.2026 21:09:39.449> posix_sys|   HOME_URL="https://www.ubuntu.com/"
[28.07.2026 21:09:39.449> posix_sys|   SUPPORT_URL="https://help.ubuntu.com/"
[28.07.2026 21:09:39.449> posix_sys|   BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
[28.07.2026 21:09:39.449> posix_sys|   PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
[28.07.2026 21:09:39.449> posix_sys|   UBUNTU_CODENAME=noble
[28.07.2026 21:09:39.449> posix_sys|   LOGO=ubuntu-logo
[28.07.2026 21:09:39.449> configpar|   Configuration content is parsed.
[28.07.2026 21:09:39.449> configpar|   Configuration content is parsed. ok.
[28.07.2026 21:09:39.449> installer|   Getting hostname.
[28.07.2026 21:09:39.449>          |     Creating child process: hostname with arguments: 
[28.07.2026 21:09:39.450>          | Thread started.  Role: 'Stdout reader, pid 2381054', thread id: 135342638233280, parent id: 135342641679232.
[28.07.2026 21:09:39.450>          | Thread started.  Role: 'Stderr reader, pid 2381054', thread id: 135342629840576, parent id: 135342641679232.
[28.07.2026 21:09:39.451> installer|       backend-public-services
[28.07.2026 21:09:39.451>          | Thread finished. Role: 'Stdout reader, pid 2381054'.
[28.07.2026 21:09:39.452>          | Thread finished. Role: 'Stderr reader, pid 2381054'.
[28.07.2026 21:09:39.452> installer|   Getting hostname. ok.
[28.07.2026 21:09:39.452> installer|   Getting fgdn.
[28.07.2026 21:09:39.452>          |     Creating child process: hostname with arguments: --fqdn
[28.07.2026 21:09:39.452>          | Thread started.  Role: 'Stdout reader, pid 2381057', thread id: 135342638233280, parent id: 135342641679232.
[28.07.2026 21:09:39.452>          | Thread started.  Role: 'Stderr reader, pid 2381057', thread id: 135342629840576, parent id: 135342641679232.
[28.07.2026 21:09:39.454> installer|       backend-public-services
[28.07.2026 21:09:39.454>          | Thread finished. Role: 'Stdout reader, pid 2381057'.
[28.07.2026 21:09:39.454>          | Thread finished. Role: 'Stderr reader, pid 2381057'.
[28.07.2026 21:09:39.454> installer|   Getting fgdn. ok.
[28.07.2026 21:09:39.454> installer| Collecting system info. ok.

Whereas in /var/log/veeamma/agent.log I see this issue:

2380991 [2380991] AgentService.Startup: Cannot validate the security certificate. Thumbprint data is missing

Then there's output from sudo veeamconfig -s and --show

mitsus@backend-public-services:/var/log/veeamma$ sudo veeamconsoleconfig -s
[sudo] password for mitsus: 
Management agent
    Connection state       : Disconnected (Required parameters are missing)
Backup agent
    Status                 : Not installed

mitsus@backend-public-services:/var/log/veeamma$ sudo veeamconsoleconfig --show
------------------- Management agent configuration ----------------------
Log file size (MB)                 : 10
Log files count                    : 10
Certificate thumbprint             : 
Deployment type                    : Remote
Cloud gateways (assigned)          : 
Cloud gateways (manually specified): vspc-cgw51.prod01.eu-west-rbx.backup.ovhcloud.com:6180
-------------------- Configuration summary ------------------------------
Tag                                : 
Management agent ID                : 7b9ea546-64c5-4c77-9d00-3dd4b479fe8f
Clustered agent ID                 : 7b9ea546-64c5-4c77-9d00-3dd4b479fe8f
Data collection interval (min)     : 120

Thanks

8

Hi @mitsus

The message “Cannot validate the security certificate. Thumbprint data is missing” confirms that the agent is not accepting the gateway’s certificate because no thumbprint has been supplied for verification.

The telnet connection works, which rules out a network‑or‑firewall connectivity problem. The failure lies in the TLS validation layer between the agent and the Veeam gateway.

To fix this, you need to provide the gateway certificate’s thumbprint when you configure the agent. To obtain the gateway certificate thumbprint you can use OpenSSL. Run this command from your server:

echo | openssl s_client -connect vspc-cgw51.prod01.eu-west-rbx.backup.ovhcloud.com:6180 -servername vspc-cgw51.prod01.eu-west-rbx.backup.ovhcloud.com 2>/dev/null | openssl x509 -fingerprint -noout | cut -d'=' -f2 | tr -d ':'

(This command should return a long string, which is the thumbprint you need)

Now you have to reconfigure the management agent with the thumbprint:

# Remove the currently configured gateway (if any)
sudo veeamconsoleconfig -g remove all

# Add the gateway with the thumbprint
sudo veeamconsoleconfig -g add vspc-cgw51.prod01.eu-west-rbx.backup.ovhcloud.com:6180 --validate_cert <THUMBPRINT_YOU_OBTAINED>

Make sure --validate_cert and the thumbprint are passed as a single argument :wink:

Restart the agent service
sudo veeamconsoleconfig --restart_service

Finally check the status
sudo veeamconsoleconfig -s

If you keep having problems, send me the Veeam logs in /var/log/veeam/ for more detailed information.

Keep me posted, cheers.
Sergio Turpín

9

Hi @sturpin,

thanks for your quick responses.

The openssl command (on the server and also on my Linux PC) throws an error:

$ echo | openssl s_client -connect vspc-cgw51.prod01.eu-west-rbx.backup.ovhcloud.com:6180 -servername vspc-cgw51.prod01.eu-west-rbx.backup.ovhcloud.com 2>/dev/null | openssl x509 -fingerprint -noout | cut -d'=' -f2 | tr -d ':'
Could not read certificate from <stdin>
406719F4927E0000:error:1608010C:STORE routines:ossl_store_handle_load_result:unsupported:../crypto/store/store_result.c:151:
Unable to load certificate

I tried other hosts and they work fine. How can I resolve this?

Thanks

Francesco

10

Hi @mitsus

If that command gives you an error, let's try it from the Veeam agent itself using the interactive method:

sudo veeamconsoleconfig -g add vspc-cgw51.prod01.eu-west-rbx.backup.ovhcloud.com:6180

Run this command without the --validate_cert argument. The agent will try to connect, and you should see a message asking you to verify the certificate. There you will see the thumbprint that the server presents.

Once you have the thumbprint you can proceed to reconfigure the agent.

# Remove the currently configured gateway
sudo veeamconsoleconfig -g remove all

# Add the gateway with the thumbprint you obtained
sudo veeamconsoleconfig -g add vspc-cgw51.prod01.eu-west-rbx.backup.ovhcloud.com:6180 --validate_cert <THUMBPRINT_YOU_OBTAINED>

# Restart the management agent service
sudo veeamconsoleconfig --restart_service

# Verify the status
sudo veeamconsoleconfig -s

If everything went well, the Connection state should appear as Connected :wink:

Let me know, cheers.
Sergio Turpín