VpsThread - Error: Unable to connect to the remote server

XProtect 2025R1

AI Bridge 2.0

Hello! I’m having a problem getting my vps devices connected. Can someone point me in the right direction?

In my device handling log I see the message: VpsThread - VpsThread - Error: Unable to connect to the remote server

The entry in the Driver Parameters looks to be correct. The host aibridge resolves from the manamgnt server to the correct address for the AI Bridge. When visiting the page in a web browser, I get a 404 not found error.

VPSNODES,http://aibridge:8787/metadata/d2034979-ecc0-455e-b750-6c1529b519a5/frigate-metadata/onvif_analytics/7467ba8a-02ac-4a6e-894d-18e2d6961806/28dc44c3-079e-4c94-8ec9-60363451eb40

d2034979-ecc0-455e-b750-6c1529b519a5 is correct for my applicaion, 7467ba8a-02ac-4a6e-894d-18e2d6961806/28dc44c3-079e-4c94-8ec9-60363451eb40 is correct for the stream ID.

When I make changes to the Driver Parameters I do see DriverParametersChanged messages in the logs.

I don’t see any VPS connections in the proxy container logs.

Hello Karl,

Are you using AI Bridge 2.0.0 after upgrading from an older version?

In 2.0.0 there is a parameter that works as a prefix to segregate URLs:

  • EXTERNAL_ROOT_PATH, located in the .env file whe running with docker-compose; or
  • externalRootPath, located under general in values.yaml when using Helm charts.

The default value for this parameter is “/processing-server”.

That parameter is used on the VPS endpoint and should look like:

http://aibridge:8787/processing-server/metadata/d2034979-ecc0-455e-b750-6c1529b519a5/frigate-metadata/onvif_analytics/7467ba8a-02ac-4a6e-894d-18e2d6961806/28dc44c3-079e-4c94-8ec9-60363451eb40

I don’t see the value on the URL you provided. Is that the case?

Thank you for the reply! I’m working with a docker-compose deployment.

When I manually add processing-server to the URL I get a connection! Thank you! This is enough for me to continue testing.

I upgraded aibridge 1.74 (not 100% on version), but copied the .env file. I’m going to try and deploy a fresh install and not include any of the files from previous versions.

Hey Karl,

Good to know that was the issue and you sovled it.

Yes, I strongly recommend you not using former version files on newer versions, despite the values you need to introduce may be the same, there could be new values that you do not need to modify from their defaults, but you need them there.

Let me know how it goes.

Regards,

Fer