<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">The AddTrust root CA certificate that our <a href="http://api.openvehicles.com" class="">api.openvehicles.com</a> is signed by has expired (last night). This will impact TLS connections to <a href="http://api.openvehicles.com" class="">api.openvehicles.com</a>. Our certificate itself is fine (and doesn’t expire until Feb 2022), but the root cert is was signed by (via intermediaries) has expired.</div><div class=""><br class=""></div><div class="">Pretty irresponsible for AddTrust/UserTrust/Comodo to sign a certificate with a later expiration date than their own CA, imho. Also irresponsible for them not to inform the customers. Everybody can be expected to monitor their own certificate expiration date, but not that of their certificate authority.</div><div class=""><br class=""></div><div class="">I’ve been up most of the night dealing with fallout from this (in other work and customer related systems), so not happy.</div><div class=""><br class=""></div><div class="">Anyway, I’ve updated the trusted root certificate in edge now, and released that. AddTrust has become UserTrust.</div><div class=""><br class=""></div><div class="">To connect via tls to <a href="http://api.openvehicles.com" class="">api.openvehicles.com</a> now, you will either need to firmware update, or manually add the trusted ca to /store/trustedca/usertrust.crt (I have attached it here, for convenience).</div><div class=""><br class=""></div><div class="">I have also taken this opportunity to change the server v2 and v3 backoff retry times to 60 seconds (was 20 or 30).</div><div class=""><br class=""></div><div class="">Regards, Mark.</div><div class=""><br class=""></div><div class=""></div></body></html>