Failed to send certificate

​@waqasali 

Hello,
if you could provide more information and details about the anomaly. Common causes Firewall blocking required ports

1. DNS/name resolution mismatch
2. Old/orphaned Veeam components on the target
3. Broken or mismatched Veeam certificates
4. Time sync issues
5. TLS / crypto policy problems (rare, but possible)

Required Ports:

1. TCP 135 (RPC)

2. TCP 445 (SMB)

3. TCP 10006 (Veeam agent management)

4. Dynamic RPC range (49152–65535 by default)

From the Veeam Backup Server:

Test-NetConnection <RemoteServerName> -Port 10006

Test-NetConnection <RemoteServerName> -Port 135

regards

Hi ​@waqasali,

We really need some more input on this. What exactly are you doing when this issue occurs? Maybe you can provide a screenshot as well.

Also provide some version numbers of VBR or agent, etc.  Putting one sentence with no other context makes trying to give suggestions next to impossible.

What certificate? In wich product? Help us to help you giving more information and details.

Open a Support Case. 

This kind of error typically requires investigation of the logs. There are many reason we could fail to push certificate, but it does not make sense to guess everyone in my opinion.

Let Veeam Support check the logs, very likely this will be related to environmental factors.

​@waqasali - Just wanted to follow up to see if you received an answer to your question. Please mark the best answer if this is resolved, including your own if needed.