Troubleshoot common issues in Azure Cosmos DB for MongoDB vCore

APPLIES TO: MongoDB vCore

This guide is tailored to assist you in resolving issues you may encounter when using Azure Cosmos DB for MongoDB vCore. The guide provides solutions for connectivity problems, error scenarios, and optimization challenges, offering practical insights to improve your experience.

Note

Please note that these solutions are general guidelines and may require specific configurations based on individual situations. Always refer to official documentation and support resources for the most accurate and up-to-date information.

Common errors and solutions

Unable to Connect to Azure Cosmos DB for MongoDB vCore - Timeout error

This issue might occur when the cluster does not have the correct firewall rule(s) enabled. If you're trying to access the cluster from a non-Azure IP range, you need to add extra firewall rules. Refer to Security options and features - Azure Cosmos DB for MongoDB vCore for detailed steps. Firewall rules can be configured in the portal's Networking setting for the cluster. Options include adding a known IP address/range or enabling public IP access.

Unable to Connect with DNSClient.DnsResponseException Error

Debugging Connectivity Issues:

Windows User:
Psping doesn't work. The use of nslookup confirms cluster reachability and discoverability, indicating network issues are unlikely.

Unix Users:
For Socket/Network-related exceptions, potential network connectivity issues might be hindering the application from establishing a connection with the Azure Cosmos DB Mongo API endpoint.

To check connectivity, follow these steps:

nc -v <accountName>.mongocluster.cosmos.azure.com 10260

If TCP connect to port 10260 fails, an environment firewall may be blocking the Azure Cosmos DB connection. Kindly scroll down to the page's bottom to submit a support ticket.

Verify your connection string:

Only use the connection string provided in the portal. Avoid using any variations. Particularly, the connection string using mongodb+srv:// protocol and the c. prefixes aren't recommended. If the issue persists, share application/client-side driver logs for debugging connectivity issues with the team by submitting a support ticket.

Next steps

If you've completed all the troubleshooting steps and haven't been able to discover a solution for your issue, kindly consider submitting a Support Ticket.