Remote Management can't connect if local was ever used
Posted: Sun Jan 05, 2020 11:26 pm
I have Blue Iris running on a machine in a closet, running as a service. I usually use another copy of Blue Iris at my desktop to manage the remote one.
I've found that if I VNC into the remote machine, and run the Blue Iris GUI (mainly to check for upgrades), then exit Blue Iris - it leaves the service thinking that a user is still connected.
When I try to run Blue Iris and connect from my desktop, I get the error "Trouble connecting, remote already connected".
The only way to clear this seems to be rebooting the Blue Iris machine, and making sure that I do NOT use the Blue Iris GUI on that machine.
Though, Reboot only works sometimes. Not working today, so I can't use Remote Management.
(and yes, both machines updated Blue Iris today)
I've found that if I VNC into the remote machine, and run the Blue Iris GUI (mainly to check for upgrades), then exit Blue Iris - it leaves the service thinking that a user is still connected.
When I try to run Blue Iris and connect from my desktop, I get the error "Trouble connecting, remote already connected".
The only way to clear this seems to be rebooting the Blue Iris machine, and making sure that I do NOT use the Blue Iris GUI on that machine.
Though, Reboot only works sometimes. Not working today, so I can't use Remote Management.
(and yes, both machines updated Blue Iris today)