Connection refused when i used NOSQLBOOSTER and Compass

[kunal_gharate]

i have installed NosqlBooster and trying to connect to altas rarely its get connected

I have whitelisted IP addresses as well as created different database users ., Tried VPN , tried firewall and antivirus enable and disable but not worked for me.

Tried on compass but same error

Even tried all stackoverflow answers

Please help me to resolve this issue.

[viraj_thakrar]

Hi @kunal_gharate,

Would like to know couple of details about your system and the way you’re connecting. Would like to know following things:

Your OS
NoSQLBooster version
Do you have any SSH details left in the SSH tab of NoSQLBooster?
Do you have any data / collection yet in the database you’re trying to access?

[Joe_Drumgoole]

I just downloaded it and connected to both a localhost MongoDB and an Atlas Cluster with NoSQLBooseter. I run a public read-only cluster at mongodb+srv://readonly:readonly@demodata.rgl39.mongodb.net/test can you try connecting to that cluster to see if it works? (yes. the username is readonly and the password is readonly, you can only query this cluster). I just verified it works with NoSQLBooster (Version 6.2.13 (6.2.13)) for me.

[kunal_gharate]

OS = WIN 10/64bit
NOSQL BOOSTER : 6.0.5

there is option for ssh in nosql
Yes in my altas have 100+ records

[kunal_gharate]

same nosqlbooster and db working for my friend

[kunal_gharate]

@Joe_Drumgoole

mongodb+srv://readonly:readonly@demodata.rgl39.mongodb.net/test

[Joe_Drumgoole]

Is this what your test URL looks like?

Are you by any chance using a proxy server that blocks port 27017?

[steevej (Steeve Juneau)]

Try switching DNS provider by using Google’s 8.8.8.8 and 8.8.4.4. It looks like your current provider does not support the new seedlist feature of modern name servers. If that is the case I would also be scared of un-installed security patches.

[Joe_Drumgoole]

Try this URL:

mongodb://readonly:readonly@demodata-shard-00-00.rgl39.mongodb.net:27017,demodata-shard-00-01.rgl39.mongodb.net:27017,demodata-shard-00-02.rgl39.mongodb.net:27017/ssl=true

This removes the SRV requirement. Note the addition of ssl=true.

[kunal_gharate]

Yes, its working on different IP address

[Joe_Drumgoole]

Does that mean that the long form URL worked? i.e. it was your name server not parsing the mongodb+srv:// URL format?

[kunal_gharate]

The issue with operating system I have reset my network setting and after that it’s working normally .