# LaunchDarkly: Client connection errors for some clients due to a recent TLS configuration change

- Impact (vendor’s label): major
- Status: resolved
- Started: 2020-05-30 06:00 UTC · Resolved: 2020-05-30 06:36 UTC · Duration: 36 min
- Updates: 1
- [Vendor status page: https://status.launchdarkly.com/incidents/3l8fg0czdfq6](https://status.launchdarkly.com/incidents/3l8fg0czdfq6)
- [Company: LaunchDarkly](https://rewindex.com/company/launchdarkly.md)

## Timeline of updates

- **resolved** 2020-05-30 06:36 UTC: This incident has been resolved. At around 10pm, we changed our certificate bundle to exclude “AddTrust External CA Root” which is scheduled to expire in a few hours and whose continued presence would interfere with connectivity to our Roku clients (see https://community.roku.com/t5/Roku-Developer-Program/Potential-service-disruption-Upcoming-SSL-certificate-expiration-could-impact-channel-operations/td-p/567871). We subsequently observed an increase in TLS negotiation failures. On investigation, we discovered that the new certificate bundle contained a valid chain that worked for all clients on most platforms but some clients on some platforms were unable to complete a valid trust chain without the presence of the removed, expiring certificate. At just after 11pm, we introduced a new intermediate certificate into our certificate bundle. This change allowed the remaining clients to establish a valid trust chain and restore their connection to our service.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/launchdarkly/incidents/3l8fg0czdfq6 · Markdown: https://rewindex.com/company/launchdarkly/incidents/3l8fg0czdfq6.md · JSON: https://rewindex.com/api/v1/companies/launchdarkly/incidents/3l8fg0czdfq6 · Generated 2026-10-18T10:31:04.187Z