What could be the issue?
Failed to send certificate, but certificate is required for remote agent management Error:
Solved
Failed to send certificate
+4Best answer by waqasali
Thank you all for your participation and feedback. The issue has been fixed. After several troubleshooting steps with support, including uninstalling the Veeam Agent on the target server, rebooting the server, and performing a fresh installation of the Veeam Agent for Windows, the problem was resolved. The backup is now working as expected.
+11
Hello,
if you could provide more information and details about the anomaly. Common causes Firewall blocking required ports
- DNS/name resolution mismatch
- Old/orphaned Veeam components on the target
- Broken or mismatched Veeam certificates
- Time sync issues
- TLS / crypto policy problems (rare, but possible)
Required Ports:
-
TCP 135 (RPC)
-
TCP 445 (SMB)
-
TCP 10006 (Veeam agent management)
-
Dynamic RPC range (49152–65535 by default)
From the Veeam Backup Server:
Test-NetConnection <RemoteServerName> -Port 10006
Test-NetConnection <RemoteServerName> -Port 135regards
+13Hi
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.
+21Also provide some version numbers of VBR or agent, etc. Putting one sentence with no other context makes trying to give suggestions next to impossible.
+11What certificate? In wich product? Help us to help you giving more information and details.
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.
+21
+4
Hello,
if you could provide more information and details about the anomaly. Common causes Firewall blocking required ports
- DNS/name resolution mismatch
- Old/orphaned Veeam components on the target
- Broken or mismatched Veeam certificates
- Time sync issues
- TLS / crypto policy problems (rare, but possible)
Required Ports:
-
TCP 135 (RPC)
-
TCP 445 (SMB)
-
TCP 10006 (Veeam agent management)
-
Dynamic RPC range (49152–65535 by default)
From the Veeam Backup Server:
Test-NetConnection <RemoteServerName> -Port 10006
Test-NetConnection <RemoteServerName> -Port 135regards
thank you for your feedback and support.
+4
Hello,
if you could provide more information and details about the anomaly. Common causes Firewall blocking required ports
- DNS/name resolution mismatch
- Old/orphaned Veeam components on the target
- Broken or mismatched Veeam certificates
- Time sync issues
- TLS / crypto policy problems (rare, but possible)
Required Ports:
-
TCP 135 (RPC)
-
TCP 445 (SMB)
-
TCP 10006 (Veeam agent management)
-
Dynamic RPC range (49152–65535 by default)
From the Veeam Backup Server:
Test-NetConnection <RemoteServerName> -Port 10006
Test-NetConnection <RemoteServerName> -Port 135regards
thank you well explained.
+4Hi
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.
Yes, you are right. At that time I did not take a screenshot, but if I face a similar issue in the future, I will include a screenshot for better clarification.
+4
Yes, sure, due to some reason I was away. Thank you for the reminder.
+4
Thank you all for your participation and feedback. The issue has been fixed. After several troubleshooting steps with support, including uninstalling the Veeam Agent on the target server, rebooting the server, and performing a fresh installation of the Veeam Agent for Windows, the problem was resolved. The backup is now working as expected.
+11Thank you for the feedback, please mark the best answer!
+21Glad to hear you were able to resolve the issue.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.