[COMPASS-5947] Can't connect to ipv6 only replicaset Created: 11/Jul/22  Updated: 29/Oct/23  Resolved: 18/Oct/22

Status: Closed
Project: Compass
Component/s: Connectivity
Affects Version/s: 1.32.2
Fix Version/s: No version

Type: Bug Priority: Critical - P2
Reporter: Ruben Herold Assignee: Le Roux Bodenstein
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

uben@work: > dpkg -l |grep compass
ii mongodb-compass 1.32.2 amd64 The MongoDB GUI
ruben@work: >

Replicaset ipv6 only version 5.0.9


Attachments: File compass-log-with-direct-connect_log.gz     File compass-log-without-direct-connect_log.gz    
Issue Links:
Depends
depends on NODE-4621 Cannot connect to IPv6 hosts with 4.9... Closed
depends on NODE-4622 Investigate why we cannot connect to ... Closed
Related
related to NODE-4621 Cannot connect to IPv6 hosts with 4.9... Closed
Documentation Changes: Not Needed

 Description   

Problem Statement/Rationale

Can't connect with compass to ipv6 only replicaset.

All servers are ipv6 only, mongo version 5.0.9 replicaset runs fine.

connection via cli runs fine. Compass won't connect. Message:

“Server selection timed out after 30000 ms” error during mongodb compass connection

 



 Comments   
Comment by Ruben Herold [ 18/Oct/22 ]

mongosh 1.6.0 seems to work.

Comment by Anna Henningsen [ 08/Sep/22 ]

rherold@via-online.de Thank you! Just to give an update, we’ve been able to reproduce this and will update this ticket once a solution becomes available.

Comment by Ruben Herold [ 24/Aug/22 ]

hi,

 

the systems are not in the same network. But I don't see any blocks in the firewall logs between.
The old mongo cli can connect. The compass can also connect if I choose direct connect I can
connect to all hosts in the replicaset.

The old cli command looks like:

mongo --ipv6 'mongodb://$USERNAME:$PASSWORD@mongo-data001.example.org,mongo-data002.example.org,mongo-arbiter001.example.org/admin?replicaSet=replica001&w=majority&authSource=admin&serverSelectionTimeoutMS=400000&readPreference=primary&connectArbiter=true'

This works without any problems.

In mongodb compass single connection to each of the hosts work also.
But if I try without direct connect it failed.

I will attach the logfiles:

compass-log-without-direct-connect_log.gz

compass-log-with-direct-connect_log.gz

 

Comment by Le Roux Bodenstein [ 23/Aug/22 ]

Can mongosh (the new shell) connect or just mongo (the old shell)?

Please provide (if possible) compass's log file and a redacted connection string.

Are the servers in the same network of the client?

This is likely an issue with how the RS is set up.

Comment by Ruben Herold [ 12/Jul/22 ]

I have checked older versions it seems that it is broken since 1.3.1

Comment by Ruben Herold [ 11/Jul/22 ]

direct connect to each server works with compass. But not to replicaset

Generated at Wed Feb 07 22:41:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.