[COMPASS-1045] "could not find config for 127.0.0.1" error connecting over SSH tunnel to Atlas free tier Created: 18/Apr/17  Updated: 27/Oct/23  Resolved: 13/May/19

Status: Closed
Project: Compass
Component/s: Atlas
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Rathi Gnanasekaran Assignee: Unassigned
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related

 Description   

Details about the bug and steps to reproduce are in the related HELP-3883



 Comments   
Comment by Massimiliano Marcon [ 13/May/19 ]

2 years old and never touched, it's probably gone away by now. If it comes up again someone will reopen it.

Comment by Thomas Rueckstiess [ 19/Apr/17 ]

Node driver supports SNI now, via the "servername" option: https://github.com/mongodb/node-mongodb-native/commit/a63de1b5f90da0a3045c53d8d6735d1349a731f9

Drivers have a testbed, which might be useful to confirm the fix. see this comment: https://jira.mongodb.org/browse/DRIVERS-320?focusedCommentId=1430776&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-1430776

It could be as simple as passing the hostname again into the node driver connection as "servername".

Proposed solution on this branch: https://github.com/mongodb-js/connection-model/commit/7db8cb10e677db79ca701d2cc47915aeb56750de

Steps to verify:

1) set up jumpbox (AWS?) with all ports open
2) follow the repro steps listed on HELP-3883
3) confirm that it's not working without the fix via Compass
4) confirm that it is working with the manual workaround
5) confirm that it is also working when using the proposed fix

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