IP Cam Talk

Welcome to the new IPCT! If you are having an issue logging in, please clear your cookies / cache.

Blue Iris UI3

Swynol

n3wb
not sure how that screenshot got their. the linked image is from imgur with that bit cut out.

i have a few other lines in a separate file. i'm guessing its the x-content-type-options


ssl_session_timeout 30m;
ssl_protocols TLSv1.2 TLSv1.1 TLSv1;
ssl_certificate E:\le64\Domain.crt;
ssl_certificate_key E:\le64\Domain.key;
ssl_session_cache shared:SSL:10m;
ssl_prefer_server_ciphers on;
ssl_ciphers ECDH+AESGCM:ECDH+AES256:ECDH+AES128:DH+3DES:!ADH:!AECDH:!MD5;


proxy_hide_header X-Powered-By;
add_header x-xss-protection 1;
proxy_hide_header X-Frame-Options;
add_header X-Content-Type-Options "nosniff" always;
add_header Strict-Transport-Security "max-age=2592000; includeSubdomains" always;
add_header 'Referrer-Policy' 'origin';
add_header Content-Security-Policy "frame-ancestors mydomain.com,subdomain.mydomain.com;";
add_header X-Frame-Options "ALLOW-FROM MyDomain | Domain Names, Web Hosting, and Free Domain Services";
 

handinpalm

Pulling my weight
Brian, I was looking through the UI3 help file for context menu and it states to "right click" to get menu. I have to "left" click for menu on chrome. I do not have my mouse setup with backwards toggle. Do you need to update description? See below:

Context Menu
If you right click (long-press on touchscreens) on an alert or clip, a context menu appears. It contains options to Flag, Protect, Download, or Delete. It also allows you to toggle a layout with larger thumbnails, or to view alert/clip properties. Admin privilege is required Flag, Protect, or Delete items.

 

bp2008

Staff member
PLEASE HELP! I've been using UI2 forever and after upgrade to 4.6.5.2. I CAN'T access the web page. App and console is fine. I get the following message under both UI2 and UI3:

An unexpected error has occurred in Blue Iris Login (version 9 / 4.6.5.2).

If you wish to report the error, please SCREENSHOT the browser now.

ReferenceError: $ is not defined
URL: http://censored_hostname/login.htm?page=/ui3beta/ui3.htm
Line: 105
Char: 3
That error means the loginScripts.js file didn't load. If you open your browser's developer tools and look in the console, there may be error messages indicating why. In @Swynol's case it is his reverse proxy server stripping out the Content-Type headers such that the browser does not trust the script.
 

CBers

Young grasshopper
In @Swynol's case it is his reverse proxy server stripping out the Content-Type headers such that the browser does not trust the script.
Is there a fix for this, as I have the same issue as well.

Also, I get the following message when I login from my phone:

"Your CPU is not fast enough to handle this stream in realtime"

Is this the phone CPU or server?

In either case, the Live streaming works fine in the mobile app, so what's different please?

Thanks.
 

Swynol

n3wb
That error means the loginScripts.js file didn't load. If you open your browser's developer tools and look in the console, there may be error messages indicating why. In @Swynol's case it is his reverse proxy server stripping out the Content-Type headers such that the browser does not trust the script.
I removed all my s cutout policies and left the basic 1 line of proxy_pass. Login screen now loads with no error, but when I attempted to login it bounces back to the login page. I also see a too many redirect error sometimes
 

mcapps

n3wb
Thanks bp2008 for putting time and effort into this. UI3 is so much better than UI2. UI2 felt like it came out in the 90s. I demo'd UI3 b15 to our management and security team and they loved it. Much more usable.
 

bp2008

Staff member
Is there a fix for this, as I have the same issue as well.

Also, I get the following message when I login from my phone:

"Your CPU is not fast enough to handle this stream in realtime"

Is this the phone CPU or server?

In either case, the Live streaming works fine in the mobile app, so what's different please?

Thanks.
Yeah, the fix is to not use a proxy server if you don't understand how to configure it to preserve headers and cookies.

The message is about your phone's CPU. The reason the official mobile app doesn't have trouble with the same stream is that it has access to a much more efficient video decoder.
 

bp2008

Staff member
I removed all my s cutout policies and left the basic 1 line of proxy_pass. Login screen now loads with no error, but when I attempted to login it bounces back to the login page. I also see a too many redirect error sometimes
If I think of it I will try to set up an nginx proxy and give it a test. I suspect your configuration is still doing unintended things.
 
Last edited:

CBers

Young grasshopper
Yeah, the fix is to not use a proxy server if you don't understand how to configure it to preserve headers and cookies.

The message is about your phone's CPU. The reason the official mobile app doesn't have trouble with the same stream is that it has access to a much more efficient video decoder.
Seems strange that BI can't cope with a RP, when most other modern services work fine.

When you click login, it does a redirect, so what is it actually redirecting to?


So UI3 isn't using the same, more efficient, video decoder then?
 

bp2008

Staff member
Seems strange that BI can't cope with a RP, when most other modern services work fine.
Blue Iris has no problem with reverse proxies that have been set up correctly.

When you click login, it does a redirect, so what is it actually redirecting to?
Once the login process is complete and you have a valid session, the login page navigates the browser window to the page indicated in the query string "page" parameter, which might be something like this:

Code:
/ui3beta/ui3.htm
If that isn't available, it navigates to the root of the site

Code:
/
Blue Iris handles requests for the root by redirecting to a valid page (jpegpull.htm, default.htm, or whatever your user's homepage is set to).

Either way, the path typically starts with a forward slash which makes it an absolute path. One common way a reverse proxy can get in the way of this is if you have it configured to listen on a path that isn't "/".

For example, this would be a bad way to configure nginx:

Code:
location /blueiris {
proxy_pass ...;
}
And this is likely to be fine:

Code:
location / {
proxy_pass ...;
}
Since I do not control the Blue Iris web server, I can't do much to make the first case more likely to work.

So UI3 isn't using the same, more efficient, video decoder then?
Since UI3 is a web page, it can only do what the web browsers make possible. Web browsers only let you use the efficient video decoders if you feed in finished video files. This adds a lot of complexity and several seconds of delay to the streaming. It would be CPU-efficient, but it would make the UI feel so glacially slow that nobody would want to use it.

The only other option available to UI3 is to decode the video with JavaScript code, which can't access hardware acceleration and is slow enough without it that most mobile devices can't handle it well.
 

adamrx7

Young grasshopper
I've held off using the new UI3 for the past few months and now that I finally have tried it I'm loving it. Big thanks for this!
 
Top