Question

Can't connect MongoDB via Shared Private Networking

Posted April 14, 2014 7.6k views
Hi, I've setup a droplet with Shared Private Networking enabled. I've provisioned it with Ubuntu 12.10 x64. Also, I've installed mongodb using 'sudo apt-get install mongodb' command. I tried using mongoose to connect to the mongodb droplet using the default port. It said failed to connect. I used the command below: > var mongoose = require('mongoose'); > mongoose.connect('mongodb://XXX.XXX.XXX.XXX:27017/database'); Things I've tried... 1. Ping the MongoDB droplet from the app droplet. It works. 2. Ran 'mongo' command on the MongoDB droplet. It works. 3. Ran 'sudo netstat -plunt' and saw the mongod process listening on the 27017 port. Any idea what I could try to verify it or what I can do to resolve this? Cheers, Mickey
Add a comment
mickey
By:
mickey

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
5 answers
me190083 April 14, 2014
Have you ever check your iptables list?
Use $iptables -S to print all the rules of your firewall.
Reply Report
mickey April 15, 2014
Yes. Here's the list.

-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT

Does it means that it accept all ports?
Reply Report
mickey April 15, 2014
It solved. The bind_ip is set to 127.0.0.1 by default. Need to change it to 0.0.0.0. Cheers.
Reply Report
kamaln7 April 15, 2014
I also recommend adding an IPTables rule that drops all packets to the MongoDB ports on the eth0 interface: 
sudo iptables -A INPUT -p tcp -m tcp -i eth0 --dport 27017 -j DROP
Reply Report
swsalim October 2, 2014

Hi, I am having the same problem. I have added the rule on IPTables and also set the bind_ip to 0.0.0.0 but always fail to connect.

What else do I need to check to pinpoint the problem?

Reply Report

Looking for something else?

Ask a new question Search for more help