http: TLS handshake error from XXX remote error: tls: bad certificate
Hello,
My telemetry server suddenly stopped working (after I changed the SSL on the http-proxy) and it errors out with : http: TLS handshake error from XXXXX: remote error: tls: bad certificate
I don't think it is related to that ssl renewal on http-proxy.
I am using Lets Encrypt for SSL on the telemetry server and I am a bit lost on what is happening. I saw other issue from other people I did check all but I am not confused in the below:
- The Lets Encrypt certs are added on the tesla-telemetry server. I had to stop httpd because telemetry server connects exclusively on it over 443. If I enable back httpd domains certs looks good, but my docker on 443 will not start as port is in use.
- The telemetry server config gets the ssls certs (from LetsEncrypt) referenced in the config.json: "tls": { "server_cert": "/etc/tesla-telemetry/certs/fullchain.pem", "server_key": "/etc/tesla-telemetry/certs/privkey.pem" },
- on my app registration I have com.tesla.3p.public-key.pem that was generated before from a private-key.pem that has nothing to do with LetsEncrypt certs.
If I try to validate with openSSL it does not work when httpd is down and only docker telemetry server is up.
803B9CBC897F0000:error:0A000412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate:ssl/record/rec_layer_s3.c:1620:SSL alert number 42
I am struck on this. Please help.
Issue has been fixed. The problem was caused by the config sent to the car that was referencing an expired SSL.