Hmmm, I think this might partially/mostly explain it, though I have allowed a tight range of IPs thru that way for some time. Probably going to move away from that going forward. I need to sign out everywhere and come in fresh again to see if the symptom clears up. I think what threw me is I am already signed in, but it seemed like a fresh unauthenticated “sign in” was superseding.
OK, that’s definitely it. I signed out everywhere and removed the IPs allowed to connect unauthenticated, and behavior is back to normal… including the auto-redirect to “/web” when using https://local_ip_addr:port only.
I am very suspicious of changes in behavior and that’s basically what this was.
Interesting.
Appreciate all the feedback as-always.
