[SERVER-44927] Unable to connect remote client on GCP Created: 03/Dec/19  Updated: 27/Oct/23  Resolved: 04/Dec/19

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: 4.2.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Vishal Deore Assignee: Backlog - Triage Team
Resolution: Community Answered Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Server Triage
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

Connect thought mongo client utility or MongoDB Atlas remotely on standalone instance deployed on GCP VM. We were facing similar issue in MongoDB Atlas instance on GCP also.

 

It seems the instance is resetting the connection, we are able to telnet the port remotely. Now open allow all in the firewall rules as well as on iptables for the underlying service.

Participants:

 Description   

We are getting the following error intermittently after verifying the server logs. It sometimes connect through atlas but have to click refresh data continuously.

2019-12-03T16:01:16.362+0000 I  ACCESS   [conn61] Successfully authenticated as principal ncr_service on pwm from client 104.129.196.84:361992019-12-03T16:01:45.442+0000 I  NETWORK  [conn61] end connection 104.129.196.84:36199 (2 connections now open)2019-12-03T16:01:46.681+0000 I  NETWORK  [listener] connection accepted from 104.129.196.84:34043 #62 (3 connections now open)2019-12-03T16:01:46.879+0000 I  NETWORK  [conn62] received client metadata from 104.129.196.84:34043 conn62: { driver: { name: "nodejs-core", version: "3.2.7" }, os: { type: "Windows_NT", name: "win32", architecture: "x64", version: "10.0.17134" }, platform: "Node.js v10.2.0, LE", application: { name: "MongoDB Compass Community" } }2019-12-03T16:01:47.589+0000 I  ACCESS   [conn62] Successfully authenticated as principal ncr_service on pwm from client 104.129.196.84:340432019-12-03T16:02:16.668+0000 I  NETWORK  [conn62] end connection 104.129.196.84:34043 (2 connections now open)2019-12-03T16:02:17.909+0000 I  NETWORK  [listener] connection accepted from 104.129.196.84:1397 #63 (3 connections now open)2019-12-03T16:02:18.109+0000 I  NETWORK  [conn63] received client metadata from 104.129.196.84:1397 conn63: { driver: { name: "nodejs-core", version: "3.2.7" }, os: { type: "Windows_NT", name: "win32", architecture: "x64", version: "10.0.17134" }, platform: "Node.js v10.2.0, LE", application: { name: "MongoDB Compass Community" } }2019-12-03T16:02:18.827+0000 I  ACCESS   [conn63] Successfully authenticated as principal ncr_service on pwm from client 104.129.196.84:13972019-12-03T16:02:47.900+0000 I  NETWORK  [conn63] end connection 104.129.196.84:1397 (2 connections now open) 



 Comments   
Comment by Dmitry Agranat [ 04/Dec/19 ]

Hi vishal.deore@techgeek.co.in,

The SERVER project is for bugs and feature suggestions for the MongoDB server. To inform our Atlas team of issues you are having or feature requests you'd like to suggest, please reach out to the Atlas support team via Intercom. You can do this by clicking the round green button at the bottom right of the cluster view page in Atlas.

Regards,
Dima

Comment by Vishal Deore [ 03/Dec/19 ]

asking it as I think it might have faced by someone in past. Note the config, mongodb.conf

 

net:  port: 27017  
#bindIp: 127.0.0.1  
# Enter 0.0.0.0,:: to bind to all IPv4 and IPv6 addresses or, alternatively, use the net.bindIpAll setting.  bindIpAll: true 

Generated at Thu Feb 08 05:07:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.