v1.29.2: Bad Certificate when using http proxy (self signed cert)

[zlymeda]

Is there an existing issue for this?

• [X] I have searched the existing issues

What happened?

Home Assistant addon is using http proxy without an issue. Using TESLA_API_HOST in teslamate fails with Bad Certificate.

I believe it is due to a self-signed certificate. I see there is already TESLA_WSS_TLS_ACCEPT_INVALID_CERTS for WebSockets. Can we have the same for the HTTP?

Thank you

Expected Behavior

to be able to use self-signed cert on HTTP proxy

Steps To Reproduce

Use HTTP proxy with self-signed cert

Relevant log output

2024-06-19 07:30:59.483 [notice] TLS :client: In state :wait_cert_cr at ssl_handshake.erl:2123 generated CLIENT ALERT: Fatal - Bad Certificate
2024-06-19 07:30:59.483 [error] GET https://pi.home:8443/api/1/vehicles/XYZ -> error: "TLS client: In state wait_cert_cr at ssl_handshake.erl:2123 generated CLIENT ALERT: Fatal - Bad Certificate\n" (78.470 ms)

Screenshots

No response

Additional data

No response

Type of installation

Docker

Version

v1.29.2