#Robo 3t and lightsail how to
How to connect to a MongoDB over SSH from Debezium.Mongodb atlas dedicated cluster: how to create peering connection with AWS and then access the cluster without whitelisting ips.How to use Compass to access remote Mongo instance via SSH tunnel?.Cannot establish connection to remote mongoDB server using ssh tunnel in class object.How to remote access gcp ports of mongodb on gcp VM?.How to access a remote mongodb through Compass?.How to save data to remote mongoDB via ssh tunnel? (connection refused).how to connect to mongodb server via ssh tunnel with Proxy Jump (Bastion Host).How to setup SSH tunnel to connect to my ElasticSearch and MongoDB residing on AWS EC2 server?.
How do I access a remote aws lightsail mongodb over ssh tunnel. What I haven't got to the bottom of is the specification of the host:port/db as an argument as per the output from running mongo -help usage: mongo ġ92.169.0.5/foo foo database on 192.168.0.5 machineġ92.169.0.5:9999/foo foo database on 192.168.0.5 machine on port 9999 The default host is localhost, so in this case it uses the tunnel, this will also just connect to the test db, you can then admin from there. T22:00:42.380+0000 E QUERY Error: couldn't connect to server 127.0.0.1:27017, connection attempt failed only command I could get to work is: mongo admin -username XXXXXX -password XXXXXX -port 8181 T22:00:42.380+0000 W NETWORK Failed to connect to 127.0.0.1:27017, in(checking socket for error after poll), reason: errno:111 Connection refused Won't work as I've omitted 'admin' from it and not specified localhost!īut mongo admin -username XXXXXX -password XXXXXX localhost:8181/testdataĭoesn't work either and gives the following output. If you need to do this then follow these instructions:Ģ) This command mongo -username XXXXXX -password XXXXXX 31.16.56.125:8181/testdata To solve this I had to run sudo apt-get purge mongodb-org* (note the asterisk). One thing I did have trouble with is that apt-get seemed to perform an update, yet the version reported when issuing the mongo command was still 2.6. 
Upgrading this solved some issues - in that I was getting a more meaningful error message. OK I've (partially) solved this, there were a few things wrong.ġ) The mongo client was 2.6 and mongo running on AWS was 3.4.
0 kommentar(er)
