I was getting the AJAX 500 message AFTER I renamed my server. I stopped the process and reinstalled and worked again.
How to pass "ajax error 500" with Windows Admin Center 24.10 (v2)
Hi there,
I did successfully deploy the new v2 of Windows Admin Center (Build 2.4.2.1, 2410). I've got a Dell HW as a server, where I have Windows Server Core 2019 running. The server core runs as a Hyper-V host. It has been nice and easy to run Hyper-V with Windows Admin Center so far but the most recent v2 seems to be causing all kinds of head-ache. Seemingly everything worked.
- WAC install can be run from admin cmd as is
- Setup TCP port as 44301 -> ok
- Check firewall -> ok
- ensuring that my star-certificate can be used -> ok
- set trusted hosts as all -> ok
- set anonymous use as ok ->
- set windows authentication as the method -> ok
- setting my own FQDN as de-facto connect point -> ok
- it even checks that PS remoting is on -> ok
- I tested via powershell that my firewall works
- starting WindowsAdminCenter service
- running from a client pc the https://FQDN:44301
- Great, it works, loads bootstrap and everything
- I get in with my admin (<local machine>\Administrator)
- Now here is where it gets funny
- I try to click to my "Server" -> "ajax error 500"
- this is so weird, no real error stack
- kind of getting a feeling that the WAC v2 is just incomplete
- How do you get pass this point?
(above the screen cap on the error after clicking my Server "Hyperpilvi" -> "Connection error")
Any ideas how to resolve this one?
2 answers
Sort by: Most helpful
-
-
Randall Okwei 16 Reputation points
2025-04-23T00:46:31.1633333+00:00 Find the machine certificate Make sure that the subject is not blank, as well manage the keys by adding the network service account with full control.