I am unfamiliar with TLS versioning. I am building my project on localhost. I ran node -p process.versions.tls in my project and it came back as “undefined”.
Here is the full error output for viz:
MongoServerSelectionError: 00560D1701000000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1605:SSL alert number 80
at Topology.selectServer (/Users/baptistefernandez/Desktop/01-refresher-starting code/refresher/node_modules/mongodb/lib/sdam/topology.js:320:38)
at async Topology._connect (/Users/baptistefernandez/Desktop/01-refresher-starting code/refresher/node_modules/mongodb/lib/sdam/topology.js:204:28)
at async Topology.connect (/Users/baptistefernandez/Desktop/01-refresher-starting code/refresher/node_modules/mongodb/lib/sdam/topology.js:156:13)
at async topologyConnect (/Users/baptistefernandez/Desktop/01-refresher-starting code/refresher/node_modules/mongodb/lib/mongo_client.js:233:17)
at async MongoClient._connect (/Users/baptistefernandez/Desktop/01-refresher-starting code/refresher/node_modules/mongodb/lib/mongo_client.js:246:13)
at async MongoClient.connect (/Users/baptistefernandez/Desktop/01-refresher-starting code/refresher/node_modules/mongodb/lib/mongo_client.js:171:13)
at async run (/Users/baptistefernandez/Desktop/01-refresher-starting code/refresher/mongo.js:54:3) {
reason: TopologyDescription {
type: 'ReplicaSetNoPrimary',
servers: Map(3) {
'cluster0-shard-00-01.95yeh.mongodb.net:27017' => [ServerDescription],
'cluster0-shard-00-00.95yeh.mongodb.net:27017' => [ServerDescription],
'cluster0-shard-00-02.95yeh.mongodb.net:27017' => [ServerDescription]
},
stale: false,
compatible: true,
heartbeatFrequencyMS: 10000,
localThresholdMS: 15,
setName: 'atlas-7bpf9y-shard-0',
maxElectionId: null,
maxSetVersion: null,
commonWireVersion: 0,
logicalSessionTimeoutMinutes: null
},
code: undefined,
[Symbol(errorLabels)]: Set(0) {},
[cause]: MongoNetworkError: 00560D1701000000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1605:SSL alert number 80
at TLSSocket.<anonymous> (/Users/baptistefernandez/Desktop/01-refresher-starting code/refresher/node_modules/mongodb/lib/cmap/connect.js:285:44)
at Object.onceWrapper (node:events:628:26)
at TLSSocket.emit (node:events:513:28)
at emitErrorNT (node:internal/streams/destroy:151:8)
at emitErrorCloseNT (node:internal/streams/destroy:116:3)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
[Symbol(errorLabels)]: Set(1) { 'ResetPool' },
[cause]: [Error: 00560D1701000000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1605:SSL alert number 80
] {
library: 'SSL routines',
reason: 'tlsv1 alert internal error',
code: 'ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR'
}
}
}
My Macbook Pro is a little old (13-inch, 2016, Two Thunderbolt 3 ports). This means that I am unable to update past the Monterey version disclosed above.
If my old hardware is the issue, is there a way for me to bypass this using Docker or else? I would really appreciate any solution. For context, this is my first time working with MongoDB so any guidance would be great.
[nodemon] starting `node app.js`
Error connecting to MongoDB: MongooseServerSelectionError: Could not connect to any servers in your MongoDB Atlas cluster. One common reason is that you're trying to access the database from an IP that isn't whitelisted. Make sure your current IP address is on your Atlas cluster's IP whitelist: https://www.mongodb.com/docs/atlas/security-whitelist/
at _handleConnectionErrors (/Users/baptistefernandez/Desktop/Backend/node_modules/mongoose/lib/connection.js:1110:11)
at NativeConnection.openUri (/Users/baptistefernandez/Desktop/Backend/node_modules/mongoose/lib/connection.js:1041:11) {
reason: TopologyDescription {
type: 'ReplicaSetNoPrimary',
servers: Map(3) {
'cluster0-shard-00-00.l23b4.mongodb.net:27017' => [ServerDescription],
'cluster0-shard-00-01.l23b4.mongodb.net:27017' => [ServerDescription],
'cluster0-shard-00-02.l23b4.mongodb.net:27017' => [ServerDescription]
},
stale: false,
compatible: true,
heartbeatFrequencyMS: 10000,
localThresholdMS: 15,
setName: 'atlas-s2vrlb-shard-0',
maxElectionId: null,
maxSetVersion: null,
commonWireVersion: 0,
logicalSessionTimeoutMinutes: null
},
code: undefined
}
[nodemon] clean exit - waiting for changes before restart
the problem is typically related to either network connectivity, i.e. you don’t have a firewall rule enabling you to connect to the cluster from your local IP address. and/or authentication credentials, i.e. you don’t have your user id and password correct.
To troubleshoot, try connecting from mongosh / command line… you’ll get some more information… please share that.