As I understand it, if you expose your BI server directly onto the internet (by configuring your home router to do so - in my view a bad idea) and set the WAN IP Address to be your router's public IP address (assigned by your ISP), when you are in a coffee shop you can use the BI App to connect...
I guess you can think of it as merging the two networks. One can get carried away with VPN setups but most people probably use the default VPN setup of sending all traffic (which includes DNS requests) from their client device to their VNP Server's local network, so it's more like when the VPN...
I preferred it when Blue Iris ran happily on a VM on a modern rack mount server.
I appreciate your suggestion of using bare metal hardware but will only consider using software that runs in a VM environment; fortunately Blue Iris does just about still manage to do so.
No luck improving my setup I'm afraid, it just seems more resource hungry now. I've not had the inclination to try moving the VM from SSD back to SAN storage.
Do please let us know if you find a solution though!
I spent a lot of time re-reading the help (the only suggestion I got from...
I've worked around the issue for the time being by moving the VM from the iSCSI LUN it has inhabited happily for the past year or so onto a local SSD (the CPU was also assigned a couple more cores, which in hindsight was probably unnecessary).
Before doing this I updated VMWare ESXi from V6.0...
An interim update:
I've managed to make the computer usable by locating the Blue Iris process in Task Manager and restricting it to use only one of the 2 available CPUs (by right-clicking the busy process in the Task Manager's "Details" tab and selecting "Set affinity"). This frees up CPU...
If you managed to resolve your issue, could you update how please?
My install's been running fine for a year or so and after updating today I seem to have the same problem. I have Blue Iris 4 on a VM running Windows 10 Pro; the Blue Iris process was consuming 30%-60% CPU, it now maxes it out)...
Many thanks, this set me on the right track; note for my Blue Iris 3 install on Windows Server 2012 R2 the registry path is: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Perspective Software\Blue Iris\Cameras (there was also a decoy path which did not have the passwords in here...