If i have mlab do i have to download mongodb full#
This led me to try the full Studio 3T on my mac, which could also connect just fine.
Oddly, I could connect from using Robo 3T inside a Parallels VM on the same machine. I was trying to connect to a mongo instance in the cloud using Robo 3T, and I was getting the "Network is unreachable" message. I had this symptom, and the ultimate fix is not yet captured in an answer here. Читайте также: Av service is not respondingĪctually, if you run dig xxx(your mongo-server) before and after you manually set DNS, you may find the response Ip differently. Sollution: Manually set DNS for your devices. If everything goes well, then you get the sollution. You can have a try on ping xxx(your mongo-server), which will use 8.8.8.8 as your DNS. Someone may had polluted this DNS server. The DNS that you are using cannot interpret your mongo host correctly. (Actually, even if they are on the same network segment, things won’t work if someone polluted your DNS server.) And they are not belong to the same network segment. For example my DNS is 172.16.* and my network gateway (execute ifconig and check en0 ) is 172.17.*. You should check your DNS and your network gateway. If you cannot get the response, that means there is something wrong with your network.
If so, that’s means you may set wrong mongo config in you Robo 3T. I think there are some things you need to check to help you know what’s the problem.įirst try to ping the mongo server in your terminal to see whether you can get responses. I also meet this problem when I use Robo 3T on Mac. The atlas servers at least require this setting, if you do not choose it, then you generally get the Network is unreachable message.Īlso if you are using Atlas then you should check the Authentication tab and select SCRAM-SHA-1, however this generally results in an authentication error not a network unreachable one. If you get the following error then you should also check the following: You must restart the service for the change to take effect Just change your bind_ip in /etc/nf from 127.0.0.1 to 0.0.0.0 then restart the service, and it works for meĪ better solution is to comment out or remove the bindIp setting from the config file /etc/nf How do I fix this? I am using Robo 3T Version 1.1 I tried same with Robomongo 1.0, and still getting the same error But when I connect with the same details in Robo 3T, it doesn’t seem to be working.
I tried connecting using MongoDB Compass and the Details and Auth are working fine and I am able to connect. I am able to connect to local database with it. I am trying to connect Robo 3T to my online database and it doesn’t seem to be working.
0 kommentar(er)
