Which port is used for telemetry?

[jbanyer]

Which network port should the telemetry service (load balancer) be listening on?

The setup instructions do not specify a port, and the config endpoint does not mention supplying a port.

I realise that the server allows specifying the listening port in server_config.json, but what port do the vehicles connect to? Is it 443?

Can you include the port in config.hostname in the telemetry config, eg "test-telemetry.com:8443"?

[Bre77]

The setup instructions do specify a port, its literally port in the server config.json

As for the vehicle config, I was under the assumption config.hostname could include a port. For example test-telemetry.com:8443. If this is not the case I am will be very interested because I was somewhat depending on this.

[Bre77]

There is an undocumented "port" variable in the vehicle config. hostname="test-telemetry.com:8443" is invalid and throws a 400 hostname="test-telemetry.com",port="8443" returns a 200, but my Model 3 is still trying port 443.

[iainwhyte]

I can confirm the config.port parameter is accepted with fleet_telemetry_config create, but ignored. Vehicle always tries to connect to port 443.
Also, it appears that you can only create fleet_telemetry_config on VIN's with OWNER, VIN's with DRIVER status you get {"response":null,"error":"LRW3xxxxxx not_found","error_description":""}

Does that means fleet telemetry is only for OWNERS? Unless there is some other reason. All other vehicle endpoints in the API work for a DRIVER vehicle with my partner authentication token...

[patrickdemers6]

Changes went out earlier this week that fix the issue of port not being used.