-
Notifications
You must be signed in to change notification settings - Fork 5
Connect Error #186
Comments
Was there any work arounds on this, getting the same behavior. Yes we are getting an new localbind port not spec'ed. Do we spec or force that port? I thought it might have something to do with the PEM file location and how I am referencing it. I can use that Pem with three mongo remote access programs without any issues. There is NO Auth. Perhaps I have to do something in the config to state that? Any recent ideas? Thanks |
enabled event logging and the issue is not the PEM file but a connection refused error. Not sure what parameter I have to force to make the mongo connection happy. Port is 27019 on the mongo end and 22 on the access end. Still not sure even when I try to force a localport bind which it want to override that. status: { message: 'Create SSH Tunnel', complete: true } CONNECT ERROR -----> status: { message: 'Connect to MongoDB', |
We are attempting to access a mongo DB via a shell as shown in your example. We are getting an error when trying to connect with the following options:
Below is how we are calling the function
The error message that we are getting is:
When we look at the status values we get:
One of the concerns that I see is that thought the port in options is defined as 27017 each time I attempt to call the connect function a different port is used. (ie: 29464 as shown above). I believe that this may be the root to the problem but unsure how to resolve. Additionally we never get to the db calls that are being used. Any ideas what could be going wrong here?
The text was updated successfully, but these errors were encountered: