I’ve seen a few posts on this one, and ran into it this morning and lost a bunch of time on it… so you don’t have to relive my pain:
Browsing to http://127.0.0.1:2113 fails with a 503.
It appears that eventstore now checks to see if there is an appropriate acl on the port and creates one if not (you’ll notice a tell-tale UAC dialog pop up asking if you want to run Network Command Shell).
You are most likely to run into this if you followed the getting started advice and created the wildcard rule.
Until the start-up check is fixed, the solution is to delete the original rule - netsh http delete urlacl url=http://+:2113/ - It’s also worth checking for duplicates with net http show urlacl - if there are any the whole thing fails silently, and worse, from the logs it all looks ok.
I recommend eventstore attempts to open the port without checking the rules, and only if this fails with the expected exception should it offer to create the rule.