Robo 3T Error: Network Unavailable

Question

I am trying to connect Robo 3T to my online database and does not seem to work. I can connect to a local database with it. I tried connecting using MongoDB Compass, and the details and Auth are working fine, and I can connect. But when I connect to the same details in Robo 3T, it does not seem to work. How to fix it? I am using Robo 3T Version 1.1 I tried the same with Robomongo 1.0 and still getting the same error

Answer 1

Just change your bind_ip in /etc/mongod.conf from 127.0.0.1 to 0.0.0.0, then restart the service and it works for me ~

Answer 2

If you get the following error, you should also check the following:

Atlas servers at least require this parameter, if you do not select it, you will receive a message "Network is unavailable."

Also, if you use Atlas, you should check the Authentication tab and select SCRAM-SHA-1, however this usually leads to an authentication error, and not to a network that is not available.

Answer 3

The best solution is to comment out or remove the bindIp parameter from the /etc/mongod.conf configuration file

You must restart the service for the change to take effect.

Answer 4

I also encounter this problem when using Robo 3T on Mac. I think we need to check something to understand what the problem is.

First try the Mongo ping server in the terminal to see if you can get the answers. If so, it means that you can set the wrong Mongo config in Robo 3T.

If you cannot get an answer, then something is wrong with your network. You must check your DNS and network gateway. For example, my DNS is 172.16.* And the network gateway (do ifconig and check en0 ) is 172.17.* . And they do not belong to the same network segment. (In fact, even if they are on the same network segment, everything will not work if someone pollutes your DNS server.)

This is a problem . The DNS you are using cannot correctly interpret your mongo host. Someone might have polluted this DNS server.

You can try ping xxx(your mongo-server) @8.8.8.8 , which will use 8.8.8.8 as your DNS. If everything goes well, then you get a solution.

Solution : manually set the DNS for your devices. For example, Google public DNS, 8.8.8.8 and 8.8.4.4.

In fact, if you run dig xxx(your mongo-server) before and after you manually configure DNS, you can find the Ip answer in different ways.

Answer 5

I had this symptom and the final correction is not yet reflected here in the answer.

I tried to connect to a Mongo instance in the cloud using Robo 3T, and I got the message "Network is unavailable."

Oddly enough, I could connect using Robo 3T inside a Parallels virtual machine on the same machine.

This made me try the full version of Studio 3T on my Mac, which could also connect normally.

I eventually discovered that there was an old point file from an ancient version of Robomongo that was causing the problem. rm -rf.config/robomongo did the rm -rf.config/robomongo thing. Now I can connect to the regular, free Robo 3T.

I guess I ended my trial over Robomongo before it was free, maybe?

Answer 6

Sorry if I was late for this, but I have been working on the same problem all morning. You have to go through a few things first so that you can easily troubleshoot

1. Restart the database from the terminal by selecting the database on the correct path and let it work in the background.
2. if the database is working, then check the local host address and replace it with 127.0.0.1 instead of the shared localhost: 27017

Answer 7

I solved this problem by starting a terminal connection.

I went to the root folder and created a folder with the name: mongo-data . Then I went to the folder where I installed mongodb, then to the bin folder and just typed in the terminal: ./mongod --dbpath ~/mongo-data/

This way you can create a connection manually. So all you have to do is try to open robo 3T.

Answer 8

This means that the mongo server is not running. You need to run the mongod command on the terminal to start the server.

if you do not have mongo db installed on your computer. Download and install from Link .

Answer 9

Run the command prompt on Windows. Go to the Mongodb bin folder through the command line and type mongod and type. Now try again

Answer 10

As mentioned above, this is probably related to BindIp, if you use mac and brew to install it, you will not find anything in /etc/mongod.conf, but you will find it in /usr/local/etc/mongod.conf

 systemLog: destination: file path: /usr/local/var/log/mongodb/mongo.log logAppend: true storage: dbPath: /usr/local/var/mongodb net: bindIp: 127.0.0.1 

Change BindIp with caution!

And the same goes for launching it to start using MongoDB manually:

mongod --config/usr/local/etc/mongod.conf

or configure autostart at login using launchd by typing:

brew services start mongodb

I also encountered corrupted data files on my local computer here:

 /usr/local/var/mongodb 

just deleted them and it worked, you can see in the log that the errors are like:

** IMPORTANT: UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.6 before attempting an upgrade to 4.0; see http://dochub.mongodb.org/core/4.0-upgrade-fcv for more details. 2018-08-01T00:15:50.220+0200 NETWORK [initandlisten] shutdown: going to close listening sockets... 2018-08-01T00:15:50.220+0200 NETWORK [initandlisten] removing socket file: /tmp/mongodb-27017.sock 2018-08-01T00:15:50.224+0200 STORAGE [initandlisten] WiredTigerKVEngine shutting down 2018-08-01T00:15:50.303+0200 STORAGE [initandlisten] Downgrading WiredTiger datafiles. 2018-08-01T00:15:50.501+0200 STORAGE [initandlisten] WiredTiger message [1533075350:501686][3594:0x7fffb492e380], txn-recover: Main recovery loop: starting at 14/3712 2018-08-01T00:15:50.598+0200 STORAGE [initandlisten] WiredTiger message [1533075350:598867][3594:0x7fffb492e380], txn-recover: Recovering log 14 through 15 2018-08-01T00:15:50.664+0200 STORAGE [initandlisten] WiredTiger message [1533075350:663976][3594:0x7fffb492e380], txn-recover: Recovering log 15 through 15 2018-08-01T00:15:50.715+0200 STORAGE [initandlisten] WiredTiger message [1533075350:715398][3594:0x7fffb492e380], txn-recover: Set global recovery timestamp: 0 2018-08-01T00:15:51.002+0200 STORAGE [initandlisten] shutdown: removing fs lock... 2018-08-01T00:15:51.005+0200 CONTROL [initandlisten] now exiting 2018-08-01T00:15:51.005+0200 CONTROL [initandlisten] shutting down with code:62

Answer 11

Start the MongoDB service from the task manager . Worked for me.

In my case, mongod and mongo.exe gave error code 100.