Hello Team,
I have recently upgraded Veeam Enterprise Manager to 12.1.1.56, upgrade is successfully however now am unable to open Veeam EA or Veeam self service restore browser. tried clearing cookies, rebooted Veeam EA however issue still persists.
Unable to open Veeam Enterprise Manager post upgrade to 12.1.1.56
Userlevel 5
+1
Userlevel 5
+1
Has anyone faced this issue, or any solution, suggestions.
Userlevel 7
+17
Hi
Did you check to see if your Veeam services are running? See the User Guide for specific services it uses:
https://helpcenter.veeam.com/docs/backup/em/em_components.html?ver=120
Userlevel 7
+20
Another thing I would check is if the SSL has expired or not for the VEM. You can update them with new following this - Updating TLS Certificates - Veeam Backup Enterprise Manager Guide
Userlevel 5
+1
Hi coolsport00,
Yes, services are up and running for both Veeam EA and VBR.
Certificate is up to date with valid expiry date under IIS, am unable to open EA console to check anything.
Userlevel 7
+20
That screenshot of IIS just shows it is using SSL not that the certificate is expired or not. If you check the Bindings section you can see the HTTPS and what SSL it is using.
The other option is to uninstall and reinstall VEM pointing to the same DB you are using now so it saves the information or start with a new DB. This will definitely fix the SSL problems as I have done this many times.
Userlevel 7
+8
hello Check in IIS if you have selected the correct certificate.
I personally solved it by changing the certificate in the “Edit bindings” on IIS\Sites\VeeamBackup.
Userlevel 7
+17
If you click the “info” icon in your web browser when attempting to connect to EM, you should then be prompted with a few options, 1 will probably say “connection is not secure” or ‘certificate is not valid’. You can then click on one of these to view your certificate to see if it’s expired or not. If expired, you can modify your cert as
hmm the error clearly states commonname issue, so it should not be expiration.
Couple of questions:
- Did you have some manually made changes to web.config in the previous version, the upgrade overwrites the file to default and thus erases changes (I was a "victim” of this)
- Can you try https://{hostname}:9443 instead of https://{FQDN}:9443
- Which TLS certificate is being served currently (Chris also asked this in a previous post)
- If its the wrong one,
@Link State posted a solution for this
- If its the wrong one,
- Is the server domainjoined or not?
Userlevel 7
+9
hmm the error clearly states commonname issue, so it should not be expiration.
Couple of questions:
- Did you have some manually made changes to web.config in the previous version, the upgrade overwrites the file to default and thus erases changes (I was a "victim” of this)
- Can you try https://{hostname}:9443 instead of https://{FQDN}:9443
- Which TLS certificate is being served currently (Chris also asked this in a previous post)
- If its the wrong one,
@Link State posted a solution for this
- If its the wrong one,
- Is the server domainjoined or not?
While this could be certificate issue, from experience, the fqdn used could pose an issue as well when SSL/TLS certificate is employed unlike when using self-signed certificate
Comment
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.