I'd like to say no changes from before, but since I can't log in, I can't say for sure.

I wouldn't recommend modifying the web.config manually in most cases. Accessing the web interface directly from the server using the http://localhost:9998 binding (you may have to add that binding to IIS if you don't have it) should get you in there to see which IP is blocked by the IDS system. Once there and unblocked, you can check out the Administrative and protocol log files to see why the IP was blocked in the first place as well.

After 12 hours, I was able to get back in. I immediately made a 2nd admin account, with 2FA and IP locked to just the server in case it happens again. I don't have localhost setup, so I'll try that as well and check the logs.