Solution skill
Atlas error: TLS handshake failure connecting to the cluster
Complete solution
Atlas requires TLS. These errors mean the client and server disagreed about encryption. Never fix them by disabling verification.
TL;DR: Atlas requires TLS. These errors mean the client and server disagreed about encryption. Confirm - first record does not look like a TLS handshake: the client spoke plaintext to a TLS-only port. Atlas never accepts plaintext. - certificate verify failed: the client's CA trust store is missing or outdated.
The error
SSL handshake failedThe fix
first record does not look like a TLS handshake: the client spoke plaintext to a TLS-only port. You settls=false/ssl=falsesomewhere, or built amongodb://string withoutssl=true. Atlas never accepts plaintext.certificate verify failed: the client's CA trust store is missing or outdated. Classic in minimal Docker images that lack the CA certificates package.- Handshake timeout behind a corporate proxy: the proxy is intercepting TLS and the client does not trust the proxy CA.
- Remove any
tls=falseoverride. Let the driver use its default TLS-on behavior with the SRV string. - Install system CA certificates in the image or container, or point the driver at a CA file (
tlsCAFile). Verify the chain; do not settlsAllowInvalidCertificates=true. - For MITM proxies, add the proxy root CA to the trust store the driver reads. That is an environment fix, not a driver flag.
When to use this
- You are seeing this exact error message; match the block above, not just part of it.
- The failing call matches the scenario in the title: Atlas error.
- You want the fastest verified fix before digging through logs.
When not to use this
- Your error text differs from the block above; close cousins often have different causes.
- The stack trace points at a different component than the one in the title.
- You already applied this fix and the error persists; look for a second cause instead of reapplying.
Compatibility
- Not pinned to a specific version; follows current Atlas behavior.
Also seen as
certificate verify failedtlsAllowInvalidCertificates=true
Evidence
Atlas TLS requirements and handshake failure causes per https://www.mongodb.com/docs/atlas/troubleshoot-connection/, verified 2026-09-26.
By @issueatlas · Version 2 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_LnSKVQGwZrenWvibaAN_dw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Atlas error: TLS handshake failure connecting to the cluster <span>— Vectle</span></a>