No access QMC and HUB after installation and cannot rebuild certificates by bootstrap

[Xabinav]

HI,

I installed QS server (February 24), During the installation I noticed that the computer name that appears automatically does not match the real hostname, I changed it in "Computer host name" field to the real hostname.  

* The computer name that appeared initially is a "Doman Control" or the servers environment. (VMware server that devised for some computers)  

* The installation is a single node environment 

After installation I can't access to HUB or QMC ("This page cannot be reached"). All services was up

* hostname that present in certificate (mmc) does not match to real hostname (appears what was received automatically installation)

I tried to recreate the certificates like here-  Did all the steps, but for no success 

https://community.qlik.com/t5/Official-Support-Articles/How-to-recreate-or-just-delete-certificates-...

I ran this command: 
"C:\Program Files\Qlik\Sense\Repository\Repository.exe" -bootstrap -iscentral -restorehostname

And the certificate generation failed, this error was received -

Fatal exception during bootstrap: Newly created client certificate not valid; root certificate can't sign new certificates; 

What else can be done to make it work? I don't know what is the exact problem 

Does the computer name have to be the same as the certification?

Thanks  

***

Some details about system and environment 

1. Windows server 2022
2. VMware server
3. Singe node environment 

[mpc · Accepted solution]

Hi, 

Maybe a GPO prevents you the creation of new certificates ? 
Can you go to Regedit.exe, and try this ? 

1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb.
2. Add ProtectionPolicy DWORD 32-bit with the value of 1.
3. Retry "C:\Program Files\Qlik\Sense\Repository\Repository.exe" -bootstrap -iscentral -restorehostname (don't forget to strat the Service Dispatcher when "Entering main phase..." is displayed

Kind regards

[Xabinav · Accepted solution]

Thanks, Eventually it works. 
I did all the steps above but now I logged-in to the server with the Service account 

[mpc]

Glad to read that !