WindowsAdminCenter error ajax 500.

[Olex123]

WindowsAdminCenter does not connect to virtual machine, ajax error 500.

In system logs error (A fatal alert was received from the remote endpoint. The TLS protocol defined fatal alert code is 46.)
Please help

 

[ChatGPT]

The issue you’re encountering with the TLS error fatal alert code 46 and an AJAX 500 error in Windows Admin Center appears to stem from misconfigured or unsupported encryption settings between the Windows Admin Center and the virtual machines it’s managing. Here’s how to troubleshoot and resolve this:

Steps to Resolve​

1. Verify TLS Protocols (Ensure Compatibility)
   • TLS error code 46 indicates that the remote endpoint (the virtual machine) rejected a connection due to an encryption mismatch. Windows Admin Center requires secure protocols to establish a connection.
   • Ensure TLS 1.2 is enabled on both the client (Windows Admin Center host) and the managed virtual machine:
     • Open Registry Editor and navigate to:
       HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols
     • Enable TLS 1.2 by adding the following keys (if they don’t exist):
       

       [TLS 1.2]

     • Client: Create a DWORD value named "Enabled" and set it to 1.
     • Server: Create a DWORD value named "Enabled" and set it to 1.
     • Reboot the machine for these changes to take effect .
2. Check Certificates for the Virtual Machine
   • If using self-signed certificates, ensure they are trusted by the Windows Admin Center host machine:
     • Export the certificate from the virtual machine.
     • Import this certificate into the Trusted Root Certification Authorities store on the Admin Center host.
3. Update Browser
   • Ensure you’re using a supported browser (Microsoft Edge or Google Chrome) since older versions may struggle with updated TLS configurations .
4. Enable HTTP/2 if Required
   • Some communication protocols via Windows Admin Center’s integrated services require HTTP/2.
   • Confirm its settings in the registry:
     • Enable HTTP/2 support at:
       HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters
     • Create or set EnableHttp2Tls to 1 and EnableHttp2Cleartext to 1. Reboot the machine afterward .
5. Update Windows Admin Center and Remote Machines
   • Make sure that both Windows Admin Center and the target virtual machine are fully updated. Outdated system configurations or versions can cause compatibility issues.
6. Logs and Deeper Diagnostics
   • Review system and application event logs for further SSL or certification errors.
     • Use Event Viewer:
     • Navigate to: Applications and Services Logs > Microsoft > Windows > Schannel.
7. Firewall and Port Configuration
   • Check if firewalls on both sides are blocking the communication ports:
     • Use Test-NetConnection in PowerShell to ensure port connectivity:
       Test-NetConnection -ComputerName <VM-IP> -Port <WAC-Port>

Follow these steps methodically, as they are likely to address the root causes of the TLS rejection and AJAX error. If issues persist, feel free to provide detailed logs for further refinement of the solution!