ApsaraDB for MongoDB:Connect to MongoDB over the public internet

This issue can occur if you added an incorrect public IP address to the allowlist. Follow these steps to find the correct public IP address of your local client:

1. Add the IP address 0.0.0.0/0 to the allowlist of the MongoDB instance.

   Warning

   0.0.0.0/0 allows any device to access the MongoDB instance. This poses a security risk and must be used with caution. If you use this entry, you must promptly remove it from the allowlist.

2. Use MongoDB Shell (mongosh) to connect to the instance.

   If you still cannot connect to MongoDB after setting the allowlist to 0.0.0.0/0, you can connect to MongoDB by using Data Management (DMS) to check whether the username, password, and authentication database are correct.

3. Run the following command to query the client information for your MongoDB Shell (mongosh) session.

   db.currentOp({"appName" : "MongoDB Shell","active" : true})

   After the command is run, the client field in the result indicates the public IP address of the client. Example output:

   mgset-xxx:PRIMARY> db.currentOp({"appName" : "MongoDB Shell","active" : true})
   {
       "inprog" : [
           {
               "desc" : "conn1591052",
               "threadId" : "48008022501120",
               "connectionId" : 1591052,
               "client" : "47.xxx.xxx.xxx:40602",
               "appName" : "MongoDB Shell",
               "clientMetadata" : {
                   "application" : {
                       "name" : "MongoDB Shell"
                   },
                   "driver" : {
                       "name" : "MongoDB Internal Client",
                       "version" : "4.0.5"
                   },
                   "os" : {
                       "type" : "Linux",
                       "name" : "Ubuntu",
                       "architecture" : "x86_64",
                       "version" : "16.04"
                   }
               },
           },
           "active" : true,
   

   Note

   If you connect to the instance using a different client, run the following command to query information for all active clients.

   db.runCommand({currentOp: 1, "active" : true})

4. Add the obtained IP address to the MongoDB instance allowlist, and remove the IP address 0.0.0.0/0.

You can connect to the instance from your local device using an SSL-VPN tunnel.

Troubleshoot a public network connection from your local client based on the symptom:

• Access is slow and you suspect network fluctuations: Restarting the instance does not resolve a network-side issue. Observe the network conditions first. If the issue persists, troubleshoot your local network or the connection provided by your Internet service provider (ISP).

• The TCP connection is established, but an ECONNRESET error occurs during the handshake: Check whether the instance allowlist is correctly configured. For a sharded cluster instance, check whether the number of connections to the Mongos nodes has reached the upper limit. If the limit is reached, restart the instance to release connections or upgrade the instance specifications. Then, temporarily connect by using the single-node connection string to rule out a load balancing issue. Use the single-node connection string only for troubleshooting, not as the regular connection method.

• A client such as Apache SeaTunnel reports No server chosen or a connection timeout: The driver may fail to identify the primary node. Use the complete ConnectionStringURI for a high-availability connection, which includes the replicaSet parameter. Alternatively, temporarily specify only the connection string of the primary node for testing. After you identify the issue, resume using the complete ConnectionStringURI.

• A data synchronization task freezes: Check the client logs for out-of-memory (OOM) or connection loss errors. Then, analyze the MongoDB connection logs to determine whether the client timed out because it could not identify the primary node. Change the connection configuration to use the complete ConnectionStringURI with the replicaSet parameter for a high-availability connection, or temporarily connect only to the primary node for testing.