Testing migration from BI4 to BI5. HTTP commands fail unless local

[logbuilder]

I've been a BI4 user on Windows 8 & 10 for several years. I'm closely integrated with Homeseer so I use http commands from BI4 to HS3 and in reverse for triggers and profile changes. I've not had any real motivation to move to BI5 until recently when I decided to move BI to its own server. Currently it shares an older windows AMD server with Homeseer and Plex. I've repurposed a windows 10 Intel I7 laptop to become my dedicated BI5 server. Seemed like a good time to move to BI5 also since it apparently has performance improvements. To build the new BI5 instance, I exported Reg from existing BI4 and then imported into new BI5 instance. Worked well as far as I can tell. Running continuous recording of 4 cameras and motion detection on all is less than 15% of CPU. Great! Old server struggled with continuous on only 1 camera and motion detection on all. BI4 was taking more than 40% of CPU.

In testing the http commands between HS3 and BI5, it seems like any http request not originating from the local machine is ignored. They all work locally just fine. From the new machine, I can issue commands against the old BI4 instance on another server just fine. Just not in reverse. Hope that makes sense. Both these machines are on the same 192.168.0.x network. They sit behind a pfSense firewall that is not blocking this traffic.

To me, this feels like a setting in BI5. I've looked but can't find anything that seems to help.

Any suggestions will be appreciated!

Robert

 

[bp2008]

Look in the Web Server tab and find the box "Bind Exclusively" and make sure it is not checked. That checkbox makes the web server limit which network interfaces it listens on, and could have the wrong thing selected.

 

[bp2008]

And if that doesn't solve it, then it is probably Windows Firewall. I like to go to the advanced configuration and create an inbound rule that allows TCP traffic on my chosen port, for all network types.

 

[logbuilder]

And if that doesn't solve it, then it is probably Windows Firewall. I like to go to the advanced configuration and create an inbound rule that allows TCP traffic on my chosen port, for all network types.

Winner Winner Chicken Dinner!!! Punching a hole in windows defender worked.

Thanks so much!

Robert