@tunnus said in UI not loading after upgrading to 26318:
This also means that I cannot use "http://reactor_host:port/diag/clear_authtrack?askauth" command to clear the block (or use any other source IP for login). Docker container stays up & running and does not exit.
By the way, I didn't fully catch this on my earlier reading, but this is not true. At least, it's not the design. Blocking only blocks a single host IP address. You should be able to make the request to the clear_authtrack endpoint from any other IP (as long as you can correctly authenticate from that IP). You definitely won't be able to do it from the same IP that got blocked, of course, but any other IP should work.
The other thing is that that endpoint will not stop the docker container. That would actually be an unexpected result (bug) for that endpoint.