-
Notifications
You must be signed in to change notification settings - Fork 169
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
Client network socket disconnected #2323
Comments
Hi @BogdanDarius, thanks for reporting this! Could you paste here the connection string replacing username, password, hostnames and any information you don't want to share with placeholders? It would be also great if you could answer few questions that would help us identifying the issue: Are you trying to connect through a proxy / VPN / tunnel of sort? Could you try to connect with Thanks a lot! |
As I stated in the issue report, it worked fine in 1.26.1 same connection string. No I dont use proxy/VPN/tunnel. This doesnt work: mongodb+srv://MY_USERNAME:MY_PASSWORD@MY_DOMAIN/?authSource=admin&authMechanism=SCRAM-SHA-256&replicaSet=rs0&readPreference=primaryPreferred&appname=MongoDB%20Compass&ssl=false This works (not using srv): mongodb://MY_USERNAME:MY_PASSWORD@rs1.mongo.MY_DOMAIN:27017,rs0.mongo.MY_DOMAIN:27017,rs2.mongo.MY_DOMAIN:27017/?authSource=admin&authMechanism=SCRAM-SHA-256&replicaSet=rs0&readPreference=primaryPreferred&appname=MongoDB%20Compass&ssl=false |
Hi @BogdanDarius we are tracking this on https://jira.mongodb.org/browse/COMPASS-4928, the work for a fix has been partially done and will be released soon. |
Fixed in 1.28.1, feel free to reopen if upgrading does not solve the issue. |
Bug Report
Current Behavior
In version 1.26.1 SRV connection when ssl is not used works as expected.
In version 1.27.1 same configuration throws an error Client network socket disconnected before secure TLS connection was established.
Code/Gist
Expected Behavior/Code
To connect to the cluster.
Environment
Possible Solution
Maybe some ssl is not set properly?
Additional Context/Screenshots
The text was updated successfully, but these errors were encountered: