@Johann_Reboulleau did you find a solution for that issue, I’m having the same problem ![]()
2024-08-26T14:34:59.613712+00:00 app[web.1]: 2024-08-26 14:34:59.613 [cluster-ClusterId{value='66cc92902f17917f89ba00e6', description='null’}-myProjectCluster-shard-00-01.ht4av.mongodb.net:27017] TRACE org.mongodb.driver.cluster - Handling description changed event for server myProjectCluster-shard-00-01.ht4av.mongodb.net:27017 with description ServerDescription{address=myProjectCluster-shard-00-01.ht4av.mongodb.net:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketWriteException: Exception sending message}, caused by {javax.net.ssl.SSLException: Received fatal alert: internal_error}}
2024-08-26T14:34:59.613764+00:00 app[web.1]: 2024-08-26 14:34:59.613 [cluster-ClusterId{value='66cc92902f17917f89ba00e6', description='null'}-myProjectCluster-shard-00-01.ht4av.mongodb.net:27017] DEBUG org.mongodb.driver.cluster - Updating cluster description to {type=REPLICA_SET, servers=[{address=myProjectCluster-shard-00-01.ht4av.mongodb.net:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketWriteException: Exception sending message}, caused by {javax.net.ssl.SSLException: Received fatal alert: internal_error}}, {address=myProjectCluster-shard-00-00.ht4av.mongodb.net:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketWriteException: Exception sending message}, caused by {javax.net.ssl.SSLException: Received fatal alert: internal_error}}, {address=myProjectCluster-shard-00-02.ht4av.mongodb.net:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoSocketWriteException: Exception sending message}, caused by {javax.net.ssl.SSLException: Received fatal alert: internal_error}}]