The following error message appears when trying to test the XCP-NG Backup Proxy.
The remote certificate was rejected by the provided RemoteCertificateValidationCallback.
Xen Hosts and backup server have been issued with the same internal CA certificate.
Additional errors appear in the logs:
System.Security.Authentication.AuthenticationException: The remote certificate was rejected by the provided RemoteCertificateValidationCallback.
Can anyone point me in the right direction? Happy to provide any additional information as required.
-
acon
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: Nov 13, 2025 6:22 am
- Full Name: Aeson Admin
- Contact:
-
Kochkin
- Veeam Software
- Posts: 94
- Liked: 41 times
- Joined: Sep 18, 2014 10:10 am
- Full Name: Nikolai Kochkin
- Contact:
Re: BETA XCP-NG - The remote certificate was rejected by the provided RemoteCertificateValidationCallback
QA folks will take a look. In the meantime is it possible to share the certificate or at it's parameters? Just to be sure we identify the issue correctly
-
acon
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: Nov 13, 2025 6:22 am
- Full Name: Aeson Admin
- Contact:
Re: BETA XCP-NG - The remote certificate was rejected by the provided RemoteCertificateValidationCallback
Thanks, Kochkin, I've sent you a PM with a link to the certificate and some logs.
-
Kochkin
- Veeam Software
- Posts: 94
- Liked: 41 times
- Joined: Sep 18, 2014 10:10 am
- Full Name: Nikolai Kochkin
- Contact:
Re: BETA XCP-NG - The remote certificate was rejected by the provided RemoteCertificateValidationCallback
Thanks!
We have a bug which causes this situation for a private CA.
The easiest workaround is to use self-signed certificates while in beta.
We also have a bit complicated workaround with DB modification which we can share if using self-signed certificates for testing is not an option. Let us know if the last one is required.
We have a bug which causes this situation for a private CA.
The easiest workaround is to use self-signed certificates while in beta.
We also have a bit complicated workaround with DB modification which we can share if using self-signed certificates for testing is not an option. Let us know if the last one is required.
Who is online
Users browsing this forum: No registered users and 1 guest