I have XProtect server running in windows. installed AI Bridge in a Ubuntu VM running in Hyper V. But I was unable to find the AI Bridge from XProtect Server as a Processing Server.
All the AI Bridge containers are running. But airbridge-int container exited after sometime. That’s the only error log I could see from the containers.
However, I could access the AI Bridge GraphQL API from windows host and also access the XProtect Management web service from Ubuntu VM. Therefore I don’t think it is an issue with connectivity. I have the Processing Server Plug-in installed.
I used the docker compose to set up the AI Bridge by following this .Is there anything additional that I have to do to see the AI Bridge from XProtect Server?
Host OS : Windows 10 Enterprise.
VM: Ubuntu 22.04 LTS
Hello Amalka, thanks for your question.
This is an expected behavior. The init container’s main purpose is to register the Processing Server with Xprotect. It only exits when it successfully connects to Xprotect, otherwise it keeps running.
Please let us know if this is not clear.
.Ok if that is the expected behavior that should be fine. But as you mentioned. Port forwarding fixed the connectivity issue.
As you instructed, I executed the following powershell script and XProtect server could identify the AI Bridge as a processing server running in Hyper-v. Thanks.
echo $wsl_ip
netsh interface portproxy add v4tov4 listenport=7200 listenaddress=0.0.0.0 connectport=7200 connectaddress=$wsl_ip
netsh interface portproxy add v4tov4 listenport=3500 listenaddress=0.0.0.0 connectport=3500 connectaddress=$wsl_ip
netsh interface portproxy add v4tov4 listenport=8787 listenaddress=0.0.0.0 connectport=8787 connectaddress=$wsl_ip
netsh interface portproxy add v4tov4 listenport=8786 listenaddress=0.0.0.0 connectport=8786 connectaddress=$wsl_ip
netsh interface portproxy add v4tov4 listenport=3100 listenaddress=0.0.0.0 connectport=3100 connectaddress=$wsl_ip
netsh interface portproxy add v4tov4 listenport=8554 listenaddress=0.0.0.0 connectport=8554 connectaddress=$wsl_ip
netsh interface portproxy add v4tov4 listenport=8555 listenaddress=0.0.0.0 connectport=8555 connectaddress=$wsl_ip
netsh interface portproxy add v4tov4 listenport=4000 listenaddress=0.0.0.0 connectport=4000 connectaddress=$wsl_ip
netsh interface portproxy add v4tov4 listenport=8443 listenaddress=0.0.0.0 connectport=8443 connectaddress=$wsl_ip
netsh interface portproxy add v4tov4 listenport=9092 listenaddress=0.0.0.0 connectport=9092 connectaddress=$wsl_ip
netsh interface portproxy add v4tov4 listenport=9002 listenaddress=0.0.0.0 connectport=9002 connectaddress=$wsl_ip
netsh interface portproxy add v4tov4 listenport=29092 listenaddress=0.0.0.0 connectport=29092 connectaddress=$wsl_ip
netsh interface portproxy show v4tov4
Hello Amalka, thanks for posting this.
This script is needed when you run AI Bridge on a WSL instance, so this could be really useful for users that want to test AI Bridge using that instead of an Ubuntu Machine.