Veeam 13 Console missing login

[ewing.ng]

We try to upgrade Veeam VBR version from 12.3.1 to 13.1 last weekend.
Upgrade progress without any error. Confirmed all Veeam service running fine in Windows VM (Windows 2022)

When I try to click the Veeam console. It doesn't show login.

I also found same issue in public
>>
https://www.reddit.com/r/Veeam/comments ... ing_login/

[vnikiforov]

Hello, Ewing,

That appears to be a technical issue - please open a support case for that and add all the logs with manual collection.

This could be related to the corporate GPO policies where settings in "SSL Cipher Suite Order" could prevent product from operating correctly.

It could also be an issue with ciphers on local server for which IIS Crypto could be used to check - TLS 1.2 and 1.3 should be enabled and these 2 are our main protocols:
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

It could also be related to VBR server certificate where it does not include "Digital Signature" and "Non-Repudiation" parameters.
https://www.veeam.com/kb4534

[ewing.ng]

Already raised case : # 08225036 - After upgrade VBR to 13.1 can't show login page
>>
Here are my findings.
1. According to the Application logs I see that antivirus is present in the system and there are some warnings regarding it.
2. In the System log I see lots of DCOM errors. DCOM is part of Windows, Veeam uses it for connections. In case there are issues with DCOM Veeam may fail.
3. Error “ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY” may point to Chromium/WebView2 HTTP/2 cipher suite enforcement failure

To resolve the issue I would suggest the following action plan:
1. Temporarily completely disable the antivirus and Windows Defender to isolate potential antivirus interference.
2. Make sure all Windows Updates are installed correctly and reboot the server (usually DCOM errors are caused by missing / corrupted Windows Updates)
3. Add the following registry values to disable HTTP/2 (that should allow to resolve the issue with accessing console / WEB UI)

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters

add 2 new DWORD (32-bit) values:

EnableHttp2Tls
EnableHttp2Cleartext

Set both values to 0
4. Reboot the server and check if you can open Web Ui / Console
>>


Added these two items in registry then rebooted. The result is same.
Due to time not enough, we need to fallback to original version first by VMware snapshot.

Checked with InfoSec team, CrowdStrike antivirus don't need to exclude Veeam file system path.