Fixing the MongoDB 'Server selection timed out' Error

Decoding the Error

Few things are more frustrating than a 30-second hang followed by a wall of red text. This error occurs when your Node.js driver tries to find a usable server in your cluster but fails to reach one before the default timeout expires.

MongoServerSelectionError: Server selection timed out after 30000 ms while waiting for a connection to the server
    at Timeout._onTimeout (/node_modules/mongodb/lib/sdam/topology.js:312:34)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7) {
  reason: TopologyDescription {
    type: 'ReplicaSetNoPrimary',
    servers: Map(3) { ... },
    setName: 'atlas-xyz-shard-0'
  }
}

The Root Cause

Think of this as a generic "I can't reach the database" signal. Your driver started the handshake process but couldn't find a healthy primary node within the allotted 30,000ms. Usually, the problem isn't your code. It's a wall between your application and the data. The most frequent blockers include:

• IP Access: Your current network IP isn't on the MongoDB Atlas allowlist.
• Firewall Restrictions: Port 27017 is blocked by your local router, corporate firewall, or cloud security group.
• DNS Failures: Your system cannot resolve the SRV record in your connection string.
• Binding Issues: For local setups, MongoDB might only be listening for internal traffic.

Step 1: Check Your IP Access List

If you are using MongoDB Atlas, start here. This is the culprit 90% of the time. Did you move from the office to a coffee shop? Your public IP changed, and Atlas is now rejecting you.

• Log in to your MongoDB Atlas dashboard.
• Navigate to Network Access under the Security tab.
• Verify if your current IP is listed. If you're working from home, click "Add IP Address" and then "Add Current IP Address".
• For cloud deployments like AWS EC2 or DigitalOcean, ensure the server's public IP or the entire VPC CIDR (e.g., 10.0.0.0/16) is whitelisted.

Step 2: Test the Plumbing with Netcat

Don't waste time debugging your JavaScript if the network path is blocked. Test the connection directly from your terminal. Use nc (netcat) to see if port 27017 is actually reachable.

# Syntax: nc -zv [hostname] [port]
nc -zv cluster0-shard-00-00.mongodb.net 27017

A successful connection returns Connection to [host] port 27017 [tcp/itls] succeeded!. If the command hangs or returns "Connection refused," your network is blocking the traffic. This often happens on corporate VPNs or public Wi-Fi that restricts non-standard ports.

Step 3: Fix DNS and SRV Record Issues

Modern MongoDB strings use the mongodb+srv:// protocol. It relies on DNS SRV records to locate cluster nodes. If your local DNS provider is slow or fails to resolve these records, the driver will time out.

Try switching your machine's DNS to Google (8.8.8.8) or Cloudflare (1.1.1.1). You can also verify the SRV record manually using this command:

nslookup -type=SRV _mongodb._tcp.your-cluster-url.mongodb.net

Step 4: Resolve Docker and Local Bindings

Are you running MongoDB in a container? By default, MongoDB might only listen on 127.0.0.1. This prevents external apps or other Docker containers from connecting. Update your mongod.conf to allow broader access:

# mongod.conf
net:
  port: 27017
  bindIp: 0.0.0.0  # Listen on all available network interfaces

In docker-compose.yml, ensure your app and database share the same network. Use the service name (e.g., mongodb://db_container:27017) rather than localhost.

Step 5: Adjust the Timeout (The Last Resort)

Sometimes the network is just slow. If you're on a high-latency connection, you can give the driver more time to find a server. Add serverSelectionTimeoutMS to your connection string. Note that this is a band-aid; it won't fix a hard firewall block.

// Increase timeout to 60 seconds
const uri = "mongodb+srv://user:pass@cluster.mongodb.net/db?serverSelectionTimeoutMS=60000";
mongoose.connect(uri);

Pro Tips for Prevention

When configuring cloud environments, miscalculating CIDR ranges is an easy mistake to make. I keep a Subnet Calculator open when setting up VPC peering. It helps ensure I'm whitelisting 10.0.1.0/24 instead of a range that doesn't actually include my app server.

Finally, always test with mongosh. If the official MongoDB Shell can't connect from your server, your Node.js app won't either. Use it to isolate whether the problem is in your environment or your code.