Skip to main content
Solved

How to reintegrate VCC with VSPC after the management agent has been uninstalled


How to reintegrate Veeam-Cloud-Connect with VSPC after the management agent has been uninstalled.

Best answer by briannBrizzy

Hi Team,

We restored the VAC database and re-deployed the agent to Cloud-Connect. However, the certificate error reappeared. Instead of entering the FQDN in the Management Agent, we used the IP address and ignored the warning. As a result, the connection between VCC and VSPC was successful, lucky no duplicate ID on the DB.

After restoring the VAC database, we noticed that other Cloud-Connect servers began displaying the same security error:
"The security certificate for the backup portal has been changed. Verify the new certificate and accept the connection to continue working with the portal."

We rebooted the affected servers, and the Management Agent started working correctly. Veeam support is still investigating why the management agent was removed from VSPC after being manually uninstalled on VCC.

VCC version: 12.1.1.56
Veeam Service Provider Console version: 8.1

@Chris.Childerhose ​@Tommy O'Shea  Much appreciated the prompt response. :)

View original
Did this topic help you find an answer to your question?

9 comments

Tommy O'Shea
Forum|alt.badge.img+3
  • Experienced User
  • 45 comments
  • March 11, 2025

Have you tried downloading the management agent and installing it again? Are you running into any errors during the process?


  • Author
  • Not a newbie anymore
  • 3 comments
  • March 11, 2025

Hi Tommy,

Thank you for swift reply.

I was experiencing some issues with the Management agent earlier getting an error “The security certificate for the backup portal has been changed Verify the new certificate and accept the connection to continue working with the portal”.

 

Tried applying the below fix didn’t work.

https://www.veeam.com/kb4130

 

I manually uninstalled the Management agent from the control panel and it removed it from VSPC.

 

Regards,

Brian

 

 


Chris.Childerhose
Forum|alt.badge.img+21

You will need to get support involved as when you try to add it back I am sure it says it already exists.  I went through this and you need to get the data out of the DB to fix it.

The other option is add the VCC server by IP vs FQDN or vice versa to VSPC again.  That will work around it from the VCC section under Configuration.


lukas.k
Forum|alt.badge.img+8
  • Influencer
  • 186 comments
  • March 11, 2025

Agreed with ​@Chris.Childerhose, I had the same issue within some lab tests.

Maybe you can share both the support case results and the s/w versions you are using.


MarkBoothman
Forum|alt.badge.img+7
  • Veeam Legend
  • 197 comments
  • March 12, 2025

I’m pretty sure its just a tweak to the config file of the agent to resolve this. I’ll try and look at my past notes to see if i can find the details


Mohamed Ali
Forum|alt.badge.img+1
  • Experienced User
  • 35 comments
  • March 12, 2025

I faced a similar issue before and it was related to the FQDN/DNS problem in VCC server and found that there was host file entry and conflict in DNS entries. 


  • Author
  • Not a newbie anymore
  • 3 comments
  • Answer
  • March 12, 2025

Hi Team,

We restored the VAC database and re-deployed the agent to Cloud-Connect. However, the certificate error reappeared. Instead of entering the FQDN in the Management Agent, we used the IP address and ignored the warning. As a result, the connection between VCC and VSPC was successful, lucky no duplicate ID on the DB.

After restoring the VAC database, we noticed that other Cloud-Connect servers began displaying the same security error:
"The security certificate for the backup portal has been changed. Verify the new certificate and accept the connection to continue working with the portal."

We rebooted the affected servers, and the Management Agent started working correctly. Veeam support is still investigating why the management agent was removed from VSPC after being manually uninstalled on VCC.

VCC version: 12.1.1.56
Veeam Service Provider Console version: 8.1

@Chris.Childerhose ​@Tommy O'Shea  Much appreciated the prompt response. :)


Chris.Childerhose
Forum|alt.badge.img+21

Not a problem always here to help and this one I have dealt with lately. 😂

Glad you were able to fix it with a DB restore. 👍


Tommy O'Shea
Forum|alt.badge.img+3
  • Experienced User
  • 45 comments
  • March 12, 2025

Happy we could help! 


Comment