I keep getting error when i try connecting node to mongodb

Syeda_Aiman · 2023-09-23T09:45:03.098Z

Yeah Thanks,It really helped me

Kabir_Khan · 2023-10-17T06:57:25.550Z

Hey!
did you figure out the olutio i am getting the same erro.

Samuel_84194 · 2023-10-20T20:12:03.998Z

Here

“One possible cause to this for Mongo Atlas in particular, is if your IP is not whitelisted. In that case, the SSL handshake fails. The error is a little misleading, but I was getting an “ERR_SSL_TLSV1_ALERT_INTERNAL_ERROR” until I whitelisted my IP address.”

Talha_laddha · 2024-04-04T21:57:39.330Z

Can you please guide me how to whitelist ip

John_Sewell · 2024-04-05T15:29:44.537Z

Instructions are in the documentation:

mongodb.com

Configure IP Access List Entries — MongoDB Atlas

When creating a deployment it should automatically add your current IP or at least give you the option.

Matei_Stefan · 2024-04-07T23:51:13.974Z

In the security section you go to “Network Access” → “Add IP Address” then select any IP address

md_salman · 2024-05-03T06:48:33.566Z

it helps me too so thank you for this post so other developer can take advantage of

Nishant_Kumar_jha · 2024-05-08T03:02:52.809Z

if you are using Any VPN or any shield like Macfree etc . off it from your settings and once try again. For me it worked.

Neo_Mokhele · 2024-07-31T12:05:13.560Z

Thank you for sharing, this helped me

Sarthak_Mahajan · 2024-08-14T11:50:04.452Z

after your mongo url add “databaseName?retryWrites=true&w=majority” this help in clearing the error::

2024-08-14T10:32:43.997Z26634a0dMongoDB connection error: MongoServerSelectionError: 809C140952780000:error:0A000438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error:../deps/openssl/openssl/ssl/record/rec_layer_s3.c:1590:SSL alert number 80

2024-08-14T10:32:43.999Z26634a0d arbiters: [],

2024-08-14T10:32:43.999Z26634a0d code: undefined

Amit_Giri · 2024-08-20T10:19:47.459Z

This also woks for me.
Thanks

Okoli_Evans · 2024-08-23T11:37:58.027Z

Thanks for this, really helped me out now

Rama_Nuril_Anwari_Bandung · 2024-09-19T11:23:23.238Z

i already whitelisted my ip but still error but if i set ip to 0.0.0.0/0 it works but i dont want to set it to 0.0.0.0/0 i want to set it to my own ip address. do you have any solution?

Clan_VI_T_NAM_TITAN · 2024-09-20T19:00:56.993Z

I added the IP address to the whitelist but it didn’t work. Even using 0.0.0.0

Alon_Berkman · 2024-09-23T18:46:46.237Z

It happened to me when I upgraded mongo node.js driver from 6.3.0 to 6.9.0.
Downgrading back to 6.3.0 and the issue is gone.

Filipe_Calixto_Oliveira · 2024-09-25T19:54:17.464Z

downgrading to 6.3 worked for me too

Filipe_Calixto_Oliveira · 2024-09-27T10:15:14.701Z

update: I updated my node version the latest LTS (v20.17.0) and everything is working fine with the new driver

Onur_Can_Ak · 2024-09-29T18:49:50.615Z

it seems there is an issuea with “6.9.0”, downgrading “6.1.0” (which I use my older projects) worked for me

fazil_MUHAMMED · 2024-09-29T18:50:23.726Z

This worked for me too!! thanks !

Alon_Berkman · 2024-10-17T20:08:12.018Z

Apparently, the issue is on version 6.9.0 which contains a breaking change:

image804×286 35.5 KB

Here are two ways I found to overcome this issue:

downgrading to a lower version (6.8.2 for ex)
passing autoSelectFamily: false overriding the default value of true

Hope someone on MongoDB will see this discussion and revert this breaking change, or alternatively - document this as a breaking change on their release notes.

P.S.
I would totally understand if this new behavior was communicated on previous release notes, allowing developers to get prepared for that (+ adding a runtime warning might do as well), but since I didn’t find any evidence for that - it is a breaking change published out on 6.9.0 without any prior notification.