@kapa.ai I get the following error message :

io.airbyte.cdk.integrations.source.relationaldb.state.FailedRecordIteratorException: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: Connector configuration is not valid. Unable to connect: Timed out after 30000 ms while waiting for a server that matches ReadPreferenceServerSelector{readPreference=primary}. Client view of cluster state is {type=REPLICA_SET, servers=[{address=mongo-db02.prod.db:27018, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketWriteException: Exception sending message}, caused by {<http://javax.net|javax.net>.ssl.SSLHandshakeException: Remote host terminated the handshake}, caused by {java.io.EOFException: SSL peer shut down incorrectly}}, {address=mongo-db01.prod.db:27018, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketWriteException: Exception sending message}, caused by {<http://javax.net|javax.net>.ssl.SSLHandshakeException: Remote host terminated the handshake}, caused by {java.io.EOFException: SSL peer shut down incorrectly}}]

Using the MongoDb v2.0.7 connector on Airbyte 2.0.1

MongoDB SSLHandshakeException: Remote host terminated the handshake The error you're seeing indicates an SSL/TLS handshake failure between the Airbyte MongoDB v2 connector and your self-managed replica set. The key part of the error is:

javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake
caused by: java.io.EOFException: SSL peer shut down incorrectly

This means the connector is attempting an SSL connection, but the MongoDB server is terminating it — typically because of a TLS configuration mismatch. Common Causes & Things to Check 1. TLS mode mismatch — Your MongoDB server may be configured with

tlsMode: allowTLS

or

preferTLS

rather than requiring TLS, or vice versa. The connector's SSL settings need to match the server's expectations. 2. Self-signed or internal CA certificate — If your MongoDB cluster uses a self-signed certificate or an internal CA, the connector's Java truststore won't recognize it, causing the handshake to fail. This is a known issue with self-managed MongoDB clusters. [Self-Signed Cert Issue] 3. SSL enabled in connection string but not on server (or vice versa) — A contributor suggested trying to explicitly set

ssl=true

in the connection string parameters (e.g.,

&directConnection=false&ssl=true

), though this may not resolve all cases. [SSLHandshake Issue] Suggested Steps • Verify TLS configuration on your MongoDB servers — Confirm whether TLS is required, allowed, or disabled on

mongo-db01.prod.db:27018

and

mongo-db02.prod.db:27018

. • Check your connection string — Ensure the

ssl

parameter in your Airbyte connection string matches the server's TLS mode. • If using a custom CA — You may need to provide the CA certificate to the connector so it can validate the server's certificate. [Self-Signed Cert Issue] • Test connectivity from the Airbyte host — If you can connect using

mongosh

from the Airbyte host, compare the TLS options used there with what's configured in Airbyte. Important Note The knowledge sources do not contain a definitive fix for this specific error in connector version 2.0.7. Both related GitHub issues were closed without a confirmed resolution. [SSLHandshake Issue] [Destination SSL Issue] I'd recommend: • Joining the Airbyte Community Slack for peer support • If you're on Airbyte Cloud, opening a support ticket 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.