Vehicle doesn't send data to Telemetry Server: config_manager_error

[JjyKsi]

I've configured Telemetry Server and able to ping it.

Checklist that I've followed:

• The request is not being terminated by load balancer
• If connecting with curl to the hostaddress:443, I can see in the Telemetry Server logs that there was a connection attempt but no certificate provided.
• I've linked the 3rd party key to the car and am able to send commands and the car receives them
• Checking with check_server_certificate.sh (can't remember the exact name for now) shows that everything is ok.
• Pinging fetch_fleet_telemetry_config returns following:
  {"response"=> {"synced"=>true, "config"=> {"hostname"=>"telemetry.ionkeep.app", "ca"=> "-----BEGIN CERTIFICATE----- SENSORED, but it's full certificate chain", "port"=>443, "fields"=>{"ChargeAmps"=>{"interval_seconds"=>60}}, "alert_types"=>["service"], "iss"=>"SENSORED just in case, but base64 presentation of public key bytes ", "aud"=>"com.tesla.fleet.TelemetryClient"}}}
• Pinging the error path returns a lot of following error:
  {"created_at"=>"2024-09-19T01:35:07.545038363Z", "error"=> "error loading config file: InvalidSignature: invalid mailbox public key: only NIST-P256 ECDH keys permitted", "error_name"=>"config_manager_error", "name"=>"7593df5d-6574-42df-b6fb-b89b4d07b66a", "txID"=>"2bae31cf-b734-47e8-b688-0ffdfdbeeee0", "vin"=>"Sensored"}]}}

So it seems that even though the vehicle is able to receive the configs, something in it prevents the vehicle from parsing it. Any idea what might be going on?