Ubuntu16.04下MongoDB授权后终端可连但Studio3T无法连接

Since you can connect successfully via the terminal, your core MongoDB authentication setup is working—this issue is almost certainly tied to how Studio3T is attempting to reach or authenticate with your instance. Let’s walk through the most likely fixes step by step:

1. Adjust MongoDB’s Bind IP Configuration #

MongoDB might be listening on specific IP addresses that Studio3T isn’t targeting. Here’s how to fix that:

• Open the MongoDB config file with sudo privileges:

  sudo nano /etc/mongod.conf
  

• Locate the net section and check the bindIp value. By default, it may be set to 127.0.0.1, but localhost sometimes resolves to IPv6 (::1) which MongoDB isn’t listening on.
  • To cover both IPv4 and IPv6, set bindIp: 127.0.0.1,::1
  • For testing purposes, you can temporarily set bindIp: 0.0.0.0 (note: this opens MongoDB to all network interfaces, so revert it after testing for security)
• Save the file and restart MongoDB:

  sudo service mongod restart
  

• In Studio3T, edit your connection and use 127.0.0.1 instead of localhost as the server address. This forces IPv4 connectivity and avoids any IPv6 resolution glitches.

2. Double-Check Studio3T’s Authentication Settings #

Even tiny misconfigurations here can break the connection:

• Confirm your connection uses Basic (MONGODB-CR or SCRAM-SHA-1) as the authentication mode.
• Verify the username (ABC) and password (XYZ) are entered exactly as you created them—MongoDB usernames and passwords are case-sensitive.
• Ensure the Authentication Database is set to admin (your user was created in this database, so this is non-negotiable).
• Switch to "Direct Connection" mode in Studio3T’s connection settings. Since this is a local single-node instance, cluster discovery can introduce unnecessary complexity that causes timeouts.

3. Rule Out Firewall or Local Network Restrictions #

Ubuntu 16.04 uses ufw by default, which might be blocking Studio3T’s connection:

• Temporarily disable the firewall to test:

  sudo ufw disable
  

• If Studio3T connects after this, re-enable the firewall and add a rule to allow local access to port 27017:

  sudo ufw allow from 127.0.0.1 to any port 27017
  sudo ufw enable
  

• Check MongoDB’s logs for more specific clues about connection failures:

  tail -n 20 /var/log/mongodb/mongod.log
  

  Look for entries about rejected connections or failed authentication attempts—this can pinpoint exactly what’s going wrong.

4. Verify Version Compatibility #

Older versions of Studio3T might have compatibility issues with newer MongoDB releases:

• Check your MongoDB version in the terminal:

  mongod --version
  

• If your Studio3T is several versions behind, download and install the latest stable release. Most compatibility issues with SCRAM-SHA-1 authentication are resolved in newer builds.

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