Express+Mongoose连接MongoDB Atlas异常：请求超时及认证失败

Let’s tackle your problems head-on—those timeouts and confusing connection messages are definitely frustrating. Here’s what’s going wrong and how to fix it:

1. The Fake "Successful Connection" Problem #

Your current connection code has a critical flaw: the callback doesn’t handle errors. Even if the connection fails, it’ll still print "Successfully connected to Mongo DB" because you’re not checking for an error parameter. That’s why removing the callback revealed the real authentication failure!

Fix your connection code to properly handle errors (use promises for cleaner code, or add the error parameter to the callback):

Option 1: Using Promises (Recommended) #

const db = require('mongoose');
require('dotenv').config(); // Make sure you load .env first!

db.connect(process.env.DB_QUERY, {
  useNewUrlParser: true,
  useUnifiedTopology: true,
  useCreateIndex: true
})
.then(() => console.log('Successfully connected to Mongo DB'))
.catch(err => {
  console.error('MongoDB connection failed:', err);
  process.exit(1); // Exit the app if connection fails—no point running without DB
});

Option 2: Using Callback with Error Handling #

const db = require('mongoose');
require('dotenv').config();

db.connect(process.env.DB_QUERY, {
  useNewUrlParser: true,
  useUnifiedTopology: true,
  useCreateIndex: true
}, (err) => {
  if (err) {
    console.error('MongoDB connection failed:', err);
    process.exit(1);
  }
  console.log('Successfully connected to Mongo DB');
});

2. Why Your Requests Are Timing Out #

When your database isn’t actually connected (despite the fake success message), any database operation (like Item.find() or item.save()) will hang indefinitely, causing your requests to timeout. Fixing the connection issue above will resolve this—but you also need to add error handling to your routes to avoid hanging requests even if something goes wrong later.

Update Your Routes with Error Handling #

GET Route

router.get('/', async (req, res) => {
  try {
    const items = await Item.find();
    res.json(items);
  } catch (err) {
    res.status(500).json({ error: 'Failed to fetch items', details: err.message });
  }
});

POST Route

router.post('/', async (req, res) => {
  try {
    const item = new Item(req.body);
    const savedItem = await item.save();
    res.status(201).json(savedItem); // Use 201 status for created resources
  } catch (error) {
    res.status(400).json({ error: 'Failed to create item', details: error.message });
  }
});

3. Double-Check Your Connection String #

Even if you’ve checked username/password, make sure your DB_QUERY in .env is in the correct Atlas format:

mongodb+srv://<YOUR_USERNAME>:<YOUR_PASSWORD>@cluster0.mongodb.net/<YOUR_DB_NAME>?retryWrites=true&w=majority

• Replace <YOUR_USERNAME>, <YOUR_PASSWORD>, and <YOUR_DB_NAME> with your actual values.
• If your password has special characters (like @, :, %), URL-encode them (e.g., @ becomes %40).

4. Verify Dotenv Setup #

Make sure you’ve installed the dotenv package (npm install dotenv) and loaded it at the very top of your main server file (before accessing any process.env variables). Without this, your DB_QUERY will be undefined, leading to connection failures.

Final Checks #

• Confirm your Atlas network access list includes 0.0.0.0/0 (you said you did this, but double-check—sometimes changes take a minute to apply).
• Ensure your Atlas user has the correct permissions (at least "readWrite" on your target database).

Once you implement these fixes, your API should connect properly and respond to requests without timing out!

内容的提问来源于stack exchange，提问作者Sabyasachi Bhoi