Gotchas are lessons learned from past tickets.
Gotcha 1: Using DDNS instead of port forwarding. Accessing the UI3 interface from the LAN using the DDNS URL is very slow.
We are not networking experts so users on the forum may have a better answer.
One possibility is the firewall settings are not set correctly.
Another possibility is usually when you use a DDNS url from within the same LAN, the traffic gets proxied through the router using a function called "NAT loopback" or "hairpin NAT". It could be that their router is bad at this. One workaround is to try the BI server's LAN address instead of the DDNS url when on the same LAN.
Gotcha 2: Login is slow. Live view fails to load or takes a minute to load.
I recommend checking CPU and memory usage on both server and client while remote viewing. Most computers these days are plenty good enough for UI3, but that isn't a guarantee. And also make security software exceptions (see Windows Tuning article), as such software can interfere with the web server connections. A poorly performing network could also cause such issues.
If CPU usage is high, consider unselecting "Require/decode all camera frames when streaming".
Gear icon in top right of Console.
Gotcha 3: Ad-blockers
See ad-blocker gotcha.
Gotcha 1: Orange Clock Warning
If you get the orange clock warning, either the fps is low for the stream or the endpoint is overloaded because the resolution (i.e. bitrate) is too high.
Run through the Windows Tuning article just to make sure Windows is not in conflict with BI.
Readjust the stream using Gear icon (bottom right).
FYI, the UI3 gear settings are just presets values in the web server encoder settings
Gotcha 2: Live view is choppy.
Symptom: Many frames are missing. The time overlay skips several seconds. The live view was delayed by several seconds.
Fix: Try increasing the fps for the group stream.
Gotcha 1: Playback is slow or choppy for recordings. 1 - 5 fps
If the live view of the same camera is streaming just fine, then there is probably not an issue with CPU or network performance. The main difference between live and clip playback is the involvement of the storage device on the BI server. It may be having trouble seeking and reading an existing file if there is a lot of recording going on.
1) Revisit Gotcha 1 above in the Live view section. Simplify the stream coming to BI using the gear icon.
2) Make sure playback in UI3 is set to 1x speed and not playing in reverse.
3) Try temporarily disabling recording on the BI server (set shield to red) to reduce disk load for testing purposes.
4) Make sure the recording format is BVR. I've had bad playback issues with MP4 before.
5) If hardware acceleration is used, look for the "Also BVR" checkbox in Blue Iris console > Camera Properties > Video tab. Toggle it on or off in case hardware acceleration is helping or hurting the playback somehow.
If still an issue, run through Remote device tests to rule out the server and network.
Gotcha 1: I set the UI3 timeout to 0 (i.e. never time out), but the browser still logs me out.
In General settings, users can set the UI3 idle timeout period.
Users state this setting is not being honored and UI3 still logs out. UI3 will let you know when a session disconnected because of a timeout.
If instead you received the login page, that means UI3 lost the session with BI which resulted in reloading the page which typically redirects to the login page.
It could be caused by anything that causes temporary connectivity loss, such as the network going down for 1 minute or longer, or even Blue Iris crashing. Or maybe even a session length limit applied to the Blue Iris user account. Although I think the user would realize if they had set this on all their BI systems. There certainly is not a session length limit by default.
The other possibility is the endpoint viewing UI3 is disconnecting. For example, if the endpoint is a laptop, power saving settings may have put the laptop to sleep or disconnected the laptop from the network.
Gotcha 2: Login credentials
The login page does not remember user credentials.
Like all other UI3 settings, the username, password, and "Log in automatically" checkbox state are saved in the browser's Local Storage. Local Storage can be inspected for troubleshooting purposes in the browser's developer tools. In Chrome, a person would open developer tools > Application tab > Storage > Local Storage > [address]. This will show all local storage items that exist for the selected web site. Look for the keys "bi_username", "bi_password", and "bi_rememberMe".
To make the saved credentials get lost, the browser may be clearing Local Storage regularly (such as when the tab is closed) due to security or privacy settings. Or perhaps a browser extension is responsible. Most browsers treat "Local Storage" the same as "Cookies" so most settings affecting Cookies would affect this as well.
Gotcha 1: Reduce margins between camera windows.
See Gotcha 7 in 5.5 Release notes.
Gotcha 2: Missing cameras
Below are settings that can prevent a camera from being visible on UI3.
- A camera could be marked as hidden (BI Camera Properties > General), or its webcasting could be disabled (BI Camera Properties > Webcast).
- Or the user could be logged in to the web server using a limited account that does not have permission to view all cameras.
- Or it could be that he just needs to use the Current Group dropdown in UI3 to select All cameras.
Gotcha 1: User permissions
Global settings -> Users tab
User Permissions may be restricting access
Global settings -> Users tab
The below settings restrict access to LAN and/or applies restrictions based on the schedule.
Help button in dialog has details.
The Global settings -> Web server tab -> Advanced button has other possible access restrictions.
Help button in dialog provides details.
Gotcha 2: Ad blockers
See Ad blockers gotcha.