I cannot seem to figure out how to connect my local tool “Robomongo” to my droplet running “Ubuntu MongoDB 3.0.5 on 14.04”
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.
This question was answered by @vincro:
in the “Connection” panel: Address - localhost Port - 27017
in the “SSH” panel: Address - <your_ip_or_fqdn>:22 and use a private key auth.
This will connect via port 22 and redirect traffic sent to port 27017
Mongo on your droplet is set to respond only to traffic from localhost which is where the ssh tunnel comes in handy. Running
db.serverCmdLineOpts()
from the mongoshell will tell you what it is bound to.
This question was answered by @vincro:
in the “Connection” panel: Address - localhost Port - 27017
in the “SSH” panel: Address - <your_ip_or_fqdn>:22 and use a private key auth.
This will connect via port 22 and redirect traffic sent to port 27017
Mongo on your droplet is set to respond only to traffic from localhost which is where the ssh tunnel comes in handy. Running
db.serverCmdLineOpts()
from the mongoshell will tell you what it is bound to.
This question was answered by @vincro:
in the “Connection” panel: Address - localhost Port - 27017
in the “SSH” panel: Address - <your_ip_or_fqdn>:22 and use a private key auth.
This will connect via port 22 and redirect traffic sent to port 27017
Mongo on your droplet is set to respond only to traffic from localhost which is where the ssh tunnel comes in handy. Running
db.serverCmdLineOpts()
from the mongoshell will tell you what it is bound to.
You can use ssh tunnel:
ssh -p <sshport> username@sshhost -L 27017:127.0.0.1:27017
That’s if you use the default 27017 port,
Here’s the robomongo (v 1.0.0) setup:
Connection tab
Authentication tab
Advanced tab
SSL tab
SSH tab
Beware that the private key should be in OpenSSH format. If it is the case you may convert a putty key (ppk) with the “Putty Gen” app.
Additional details and tips here.
I “kinda” figured it out: You have to open the firewall to accept incoming connections on port 22 and port 27017 using ufw (refer to Digital Ocean’s ufw tutorial)
In your droplet:
and to check if it worked:
Now you have to change your mongod.conf file:
then go to line 23 and it should read:
change it to:
(do not add extra lines or spaces to this file, even if it is a comment).
then run
and it should be active. Go to Robomongo under ‘Connection’ tab:
Address: your droplet address
connect normally. I “kinda” figured it out because you cannot use this solution in production because it will accept any incoming IP connection to your database; which is not recommended. If I figure out how to do it with the tunnel or in a way that accepts only IPs authorized; I’ll let you know!
I “kinda” figured it out: You have to open the firewall to accept incoming connections on port 22 and port 27017 using ufw (refer to Digital Ocean’s ufw tutorial)
In your droplet:
and to check if it worked:
Now you have to change your mongod.conf file:
then go to line 23 and it should read:
change it to:
(do not add extra lines or spaces to this file, even if it is a comment).
then run
and it should be active. Go to Robomongo under ‘Connection’ tab:
Address: your droplet address
connect normally. I “kinda” figured it out because you cannot use this solution in production because it will accept any incoming IP connection to your database; which is not recommended. If I figure out how to do it with the tunnel or in a way that accepts only IPs authorized; I’ll let you know!
I “kinda” figured it out: You have to open the firewall to accept incoming connections on port 22 and port 27017 using ufw (refer to Digital Ocean’s ufw tutorial)
In your droplet:
and to check if it worked:
Now you have to change your mongod.conf file:
then go to line 23 and it should read:
change it to:
(do not add extra lines or spaces to this file, even if it is a comment).
then run
and it should be active. Go to Robomongo under ‘Connection’ tab:
Address: your droplet address
connect normally. I “kinda” figured it out because you cannot use this solution in production because it will accept any incoming IP connection to your database; which is not recommended. If I figure out how to do it with the tunnel or in a way that accepts only IPs authorized; I’ll let you know!
I “kinda” figured it out: You have to open the firewall to accept incoming connections on port 22 and port 27017 using ufw (refer to Digital Ocean’s ufw tutorial)
In your droplet:
and to check if it worked:
Now you have to change your mongod.conf file:
then go to line 23 and it should read:
change it to:
(do not add extra lines or spaces to this file, even if it is a comment).
then run
and it should be active. Go to Robomongo under ‘Connection’ tab:
Address: your droplet address
connect normally. I “kinda” figured it out because you cannot use this solution in production because it will accept any incoming IP connection to your database; which is not recommended. If I figure out how to do it with the tunnel or in a way that accepts only IPs authorized; I’ll let you know!
I “kinda” figured it out: You have to open the firewall to accept incoming connections on port 22 and port 27017 using ufw (refer to Digital Ocean’s ufw tutorial)
In your droplet:
and to check if it worked:
Now you have to change your mongod.conf file:
then go to line 23 and it should read:
change it to:
(do not add extra lines or spaces to this file, even if it is a comment).
then run
and it should be active. Go to Robomongo under ‘Connection’ tab:
Address: your droplet address
connect normally. I “kinda” figured it out because you cannot use this solution in production because it will accept any incoming IP connection to your database; which is not recommended. If I figure out how to do it with the tunnel or in a way that accepts only IPs authorized; I’ll let you know!
in the “Connection” panel: Address - localhost Port - 27017
in the “SSH” panel: Address - <your_ip_or_fqdn>:22 and use a private key auth.
This will connect via port 22 and redirect traffic sent to port 27017
Mongo on your droplet is set to respond only to traffic from localhost which is where the ssh tunnel comes in handy. Running
db.serverCmdLineOpts()
from the mongoshell will tell you what it is bound to.in the “Connection” panel: Address - localhost Port - 27017
in the “SSH” panel: Address - <your_ip_or_fqdn>:22 and use a private key auth.
This will connect via port 22 and redirect traffic sent to port 27017
Mongo on your droplet is set to respond only to traffic from localhost which is where the ssh tunnel comes in handy. Running
db.serverCmdLineOpts()
from the mongoshell will tell you what it is bound to.in the “Connection” panel: Address - localhost Port - 27017
in the “SSH” panel: Address - <your_ip_or_fqdn>:22 and use a private key auth.
This will connect via port 22 and redirect traffic sent to port 27017
Mongo on your droplet is set to respond only to traffic from localhost which is where the ssh tunnel comes in handy. Running
db.serverCmdLineOpts()
from the mongoshell will tell you what it is bound to.in the “Connection” panel: Address - localhost Port - 27017
in the “SSH” panel: Address - <your_ip_or_fqdn>:22 and use a private key auth.
This will connect via port 22 and redirect traffic sent to port 27017
Mongo on your droplet is set to respond only to traffic from localhost which is where the ssh tunnel comes in handy. Running
db.serverCmdLineOpts()
from the mongoshell will tell you what it is bound to.in the “Connection” panel: Address - localhost Port - 27017
in the “SSH” panel: Address - <your_ip_or_fqdn>:22 and use a private key auth.
This will connect via port 22 and redirect traffic sent to port 27017
Mongo on your droplet is set to respond only to traffic from localhost which is where the ssh tunnel comes in handy. Running
db.serverCmdLineOpts()
from the mongoshell will tell you what it is bound to.