[SOLVED] UI3 web server - wrong IP address

[hewini]

Blue Iris 5
Release: 5.3.1.3 x64 (2020-07-28)

I have a problem to assign the correct IP to to the UI3 web server. I want to use 192.168.99.117:81, but Blue Iris assign 172.17.161.97:81 and I cant seem to change this. This has been working before and I do not know what happend. Please see attached picture. I have tried to restart Blue Iris and the host computer.

Does anyone know how to fix this? Should it not be enough to specify the desired IP in "Local, internal (LAN) access?

[Thixotropic]

What happens if you select the IP you want, click the "Bind exclusively" checkbox, and save the settings?

Does it revert back, or...?

[hewini]

That does not seem to do anything at all. The UI3 web interface is still only reachable från 172.17.161.97:81. Could it be a bug?

[Lethargus]

Given it shows the IP you want (if I read that screenshot correctly), and you don't have bind exclusively checked, you should be able to access the web server at that IP address. If you're not able to then it's not likely BI5's fault, but something wrong in your networking. Check firewalls. When bind exclusively isn't checked it seems to bind to 0.0.0.0 which means any and all interfaces will work, they just might not get recognized as LAN right away and will present the login prompt (my current problem.) So if it's not even presenting that login you definitely have a networking issue and not a BI5 issue.

[hewini]

Thanks for your reply. I will try and find some other issue on the server. One thing I might suspect is the Docker-installation that is using hyper-V.

But the weird this is that the other IP (172.x.x.x) is working, and this is regardless of the IP I set in the drop-down list.

/Henrik

[hewini]

SOLVED!

So, I have really no idea why this is or what the original problem was. But I did a "reset settings" of the Chrome browser and this fixed my issue.

/Henrik

[Matts1984]

LOL, I wouldn't have guessed that and can't completely understand how that fixed it.... but hey, if it ain't broke (anymore) don't fix it.

Glad you got it resolved and THANK YOU for posting the solution.