为什么本地 Robo3t 连接到远程 Mongo 数据库实例，但 NodeJs 失败并出现 IP 白名单错误？

Question

I am having issues connecting to MongoDb running remotely, and the connection error response I am getting from the server is somewhat weird.

My network access whitelist is set to allow all (0.0.0.0/0). Hence, my local robo3t installation was able to connect. However, I could not connect from my NodeJs code. Error is: "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"

IP whitelist seems to be an unlikely error, given that my local robo3t client is able to connect remotely to the same remote Mongo Atlas instance, as IP whitelist is allow-all.

How do I debug this kind of thing, please?

UPDATE: this is how I connect to MongoDb. Works well on local, too.

try {
    const connectionString =
        process.env.APP_ENV == "test"
            ? await getInMemoryMongoDbAdapter()
            : `mongodb://${process.env.MONGODB_HOSTNAME}:${process.env.MONGODB_PORT}/${process.env.CBT_DATABASE_NAME}`;

    logger.info(`Connecting to MongoDB service: ${connectionString}`);
    

    await mongoose.connect(connectionString, {
        useNewUrlParser: true,
        useUnifiedTopology: true,
    });
} catch (error) {
    reject(error);
}

The logger line correctly shows: Connecting to MongoDB service: mongodb://<user>:<password>@cluster0-xxx.yyy.zzz.net:<port>/<database>

UPDATE 2 : My localhost also does not connect via this node app; whereas my robo3t (local MongoDb client) connects. I guess that means Heroku-specific issues can now be comfortably ruled out

Answer 1

A decade later, I found that for the connection parameters, I needed to supply the authSource and ssl options, as below:

{
    useNewUrlParser: true,
    useUnifiedTopology: true,
    authSource: "admin",
    ssl: true,
}

Neither one works without the other. Big shout-out to @darklightcode for all the insights he gave, leading me to dig deeper. Thanks man!