Skip to main content

Quick Tip - Fixing VSA connection to VSPC after SSL update

  • July 6, 2026
  • 0 comments
  • 5 views

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

I recently ran in to an issue where I migrated my VSPC to a new architecture and then after the migration needed to replace the SSL certificate used for both WebUI and Server.  Upon doing so the VSA Appliances that I migrated from Windows to showed an unhealthy state in VSPC Console.  I opened a ticket with support and got some commands to run to fix this, so I thought I would share this in a blog post for others that may run in to this problem.

Blog post - VSA Disconnects from VSPC Console after SSL Update

 

VSA Disconnects from VSPC Console after SSL Update

 

Introduction

 

I was recently doing some work with VSPC where we are migrating to a new architecture using the Frontend, Backend, and SQL server deployment. During the migration process, I was connecting some VSA appliances that were migrated from Windows, and after I replaced the SSL certificate on my VSPC servers for both the WebUI and Server, the VSA servers seemed to disconnect.

I opened a ticket with support and with their help got some tips on how to resolve this issue when you do change your SSL certificate with a new one. I will outline the process below.

 

VSA Certificate Fix

 

The following steps are required to address the issue with the VSA connection to the VSPC Portal -

  1. Open your VSPC Console Web UI and go to Configuration > Certificates
  2. Highlight the “Server” certificate shown in the Type column and click the Show Certificate button
  3. Copy the Thumbprint for the SSL certificate which will be used in one of the following steps
  4. Request Root Shell Access for your VSA appliance and approve it with the Veeam Security Officer
  5. Open the console of the VSA appliance in your hypervisor
  6. Log in using the Veeam Admin account and credentials including MFA code
  7. Navigate to the Remote Access Configuration menu
  8. Select the Enter Root Shell option which will drop you down to a command line to run the following three steps to check, verify and update the thumbprint as well as verify again the connection to VSPC

veeamconsoleconfig –show

veeamconsoleconfig -s

veeamconsoleconfig –validate_cert cert_thumbprint

Commands run to check VSPC Agent and SSL thumbprint, as well as command to fix and verify new thumbprint

After running the commands and getting a successful connection status, it can take up to 15 minutes for the VSPC Console to refresh and show a Healthy state.

 

Closing

 

As you can see, the fix for the VSA connection to VSPC Console after an SSL certificate update is fairly simple and straightforward. I hope this helps anyone who runs in to this problem, which allows you to fix it yourself.