Ok, that particular failure is tricky.
It shows that UI3's first script request got denied (redirected to login). This happens when
Blue Iris does not receive a session string from the web browser, or if the session string is invalid or expired.
Here's the tricky part. You literally just logged in and got a new session and used it to load ui3.htm. So we know your session is not invalid, and is not expired. The only likely explanation therefore is that the session string did not get communicated to Blue Iris at all during this script request.
The session string would have been in an HTTP cookie. There are two reasons the cookie might not have reached Blue Iris.
Either:
1) The web browser might have cookies
disabled, but lied to UI3 by telling UI3 that cookies are
enabled. I haven't heard of this happening with a recent/modern browser, however it would be worth looking into the Safari settings to be sure that cookies are enabled.
or
2) A proxy server could have stripped the cookies out of the requests or responses. A proxy server could be something you set up like "stunnel" or "nginx" or it could be part of an antivirus / antimalware program that you installed on your mac and ipad, or on the Blue Iris PC, or maybe even on your router.
If you can figure out (and tell me) exactly what is causing the cookie to be lost, maybe I can reproduce the problem on my end and fix it. UI3 does have the ability to operate without cookies, but the way it is currently coded, it only activates this ability if the browser says that cookies are disabled. Which your browser did not do.