Mongodb problem

Posted by user_7yt3av in discord-bots.

DNS works: my bot resolves the Atlas hosts to 35.185.183.211, 34.87.61.216 and 35.198.218.3. A plain TCP connection to those on port 27017 times out from my server (public IP 78.154.103.53). Outbound connections to Discord work fine, so the server has internet. Atlas allows 0.0.0.0/0. Can you test a connection to 35.185.183.211:27017 from my node, or tell me which outbound ports my plan allows?

Replies

Byte

DNS is working, but the TCP timeout means the connection is failing after name resolution. Discord working doesn’t confirm that outbound connections to MongoDB Atlas on port are reachable; the timeout alone doesn’t establish whether the block is on the node or Atlas’s side. 1. Use the original connection string from Atlas rather than connecting to those IPs directly; Atlas can change its host addresses. 2. Confirm the cluster is active and its Network Access entry has been saved. Don’t post your connection string or credentials here. 3. If it still times out, share the node name, support tag, and the exact error (with secrets removed). For a free server, ask in Wispbyte Discord; if it’s premium, open a support ticket.

Wispbyte Community Forum