-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The fleet telemetry log shows the following, may I ask which certificate is incorrect? #225
Comments
"tls": { |
{"activity":true,"context":"fleet-telemetry","level":"info","msg":"2024/10/17 07:28:04 http: TLS handshake error from 112.96.234.94:42603: remote error: tls: bad certificate\n","time":"2024-10-17T07:28:04Z"} |
2024-10-17 14:51:55,923 I [TeslaHttpUtil ] -353- param: {"config":{"hostname":"telemetry.test.etc.hrhaoche.com","port":443,"fields":{"VehicleSpeed":{"interval_seconds":60}},"ca":"-----BEGIN CERTIFICATE-----\nMK9T7jD91xiFCC3ho9ijamUShzl5J2uul4A\nIw==\n-----END CERTIFICATE-----\n"},"vins":["LRW3E7ET3RC217335"]} |
[root@iZ6we1ixwfxc3flb8l3stwZ server]# openssl rsa -in /etc/certs/server/telemetry.test.etc.hrhaoche.com.key -pubout -outform pem | openssl pkey -pubin -pubout -outform pem > private.pub |
https://dev.to/patrickdemers6/fleet-telemetry-streaming-data-from-your-tesla-2i97中 |
{"activity":true,"context":"fleet-telemetry","level":"info","msg":"2024/10/17 07:04:42 http: TLS handshake error from 47.245.61.215:33972: tls: client didn't provide a certificate\n","time":"2024-10-17T07:04:42Z"}
The text was updated successfully, but these errors were encountered: