Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fail to connect the Azure Cosmos DB for MongoDB cluster in VS Code with Firewall enabled #2416

Open
v-ruizh opened this issue Nov 14, 2024 · 1 comment
Assignees
Labels
AT-CTI Created by CTI team MongoDB Clusters
Milestone

Comments

@v-ruizh
Copy link

v-ruizh commented Nov 14, 2024

OS: Windows 10
Build Version: 20241114.1
Regression: Not a Regression

Repro Steps:

  1. Create an Azure Cosmos DB for MongoDB cluster in Azure portal.
  2. Expand the Azure Cosmos DB for MongoDB (vCore) node in VS Code -> Expand the Azure Cosmos DB for MongoDB cluster -> Enter the password to connect to the cluster.
  3. Check whether succeeds to connect the Azure Cosmos DB for MongoDB cluster or not.

Expect:
Succeed to connect the Azure Cosmos DB for MongoDB cluster.

Actual:
Fail to connect the Azure Cosmos DB for MongoDB cluster.
Image

More Info:
This issue can be fixed if setting the network as below in portal.
Image

@v-ruizh v-ruizh added the AT-CTI Created by CTI team label Nov 14, 2024
@tnaum-ms tnaum-ms self-assigned this Nov 19, 2024
@tnaum-ms tnaum-ms added this to the 0.24.2 milestone Nov 19, 2024
@tnaum-ms tnaum-ms changed the title Fail to connect the Azure Cosmos DB for MongoDB cluster in VS Code Fail to connect the Azure Cosmos DB for MongoDB cluster in VS Code with Firewall enabled Feb 27, 2025
@tnaum-ms
Copy link
Collaborator

It looks like we should:

  • attempt to detect the type of the connection error, however, detecting connectivity issues caused by a firewall configuration is not feasible
  • we should be able to discover the current firewall configuration and
    • Compare it with user's IP and act ahead of the connection attempt (best UX)
      • Potential issues with parsing IP ranges etc.
      • Potential issues with detecting the correct IP of the user
    • Suggest adding a Firewall exception in case of a connectivity issue (somehow okaysh UX)
      • easier, but not user friendly
      • an update to a firewall rule might take time to propagate.
    • ?

@tnaum-ms tnaum-ms modified the milestones: 0.25.1, 0.26.0 Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AT-CTI Created by CTI team MongoDB Clusters
Projects
Development

No branches or pull requests

2 participants