I have Meteor running on a local virtual machine on Windows which is accessible using the IP address of 192.168.56.111
When I use Robomongo, I use this IP address and point it to port 3001 and I an unable to connect.
Should I expect it to connect? If not, is there anything I need to do to get it to connect?
Setup SSH server on Windows and then simply create SSH tunnel:
ssh -L27018:192.168.56.111:3001 user#host
After that open Robomongo and connect to localhost:27018. That's it!
This technique I'm using successfully to connect to production database.
With meteor the database that runs is bound to 127.0.0.1, so it will not be accessible on other IPs. I think this was done for a security reason, though not sure.
You should use the local IP/127.0.0.1 instead of 192.168.56.11.
Related
I installed openstack using packstack. But I don't know how to configure network.
I want to access my instance using ssh like this.
Is it possible to do this?
By default, Packstack creates an "external" network that is entirely contained inside the host. This is great for creating a cloud without any knowledge of the network environment, but prevents you from accessing instances from outside.
Configure your Packstack so that its external network is your network. This is documented at https://www.rdoproject.org/networking/neutron-with-existing-external-network/.
Actually, without external network its not possible.Your instance should have external(public) ip.I'm using this way but you have other option like proxy.
if your Centos7 machine can connect your instance;
Use HaProxy at Centos machine and proxy instance ssh port to specific centos7 port and connect using this port.I'm using this way on microstack.
firebase command firebase emulators:start all ports and hosts work fine on my pc but but if I try from different device in my network (ohter pc) to access network-ip:8080 I get connection refused.
This does not worked:
firebase.firestore().useEmulator("0.0.0.0", 8080);
But this worked:
firebase.firestore().useEmulator("192.168.x.x", 8080);
Why first one was not working but second one worked did not understand the reason behind this
0.0.0.0 is not a valid destination address for outgoing connections, such as those being made by the Firebase SDK to connect to the emulator. It is only a valid incoming address for services that want to listen on all possible IP addresses assign to the machine where it's running.
I recommend doing a web search for "ip address 0.0.0.0" to read more.
Are you sure that the port that you are trying to connect to is opened? I ran through the same issue with Ubuntu firewall blocking the request. If you are using Ubuntu use this command to open the port.
sudo ufw allow 9299
I recently migrated a site to a new server and am now trying to replace the old domain by the new one using this tool suggested in the wordpress codex.
The SQL instance and the VM are both in the same region and are connected using a cloud sql proxy, however when I try and connect to the database via the searc-replace tool, I get connection refused:
EDIT:
The command used to start the sql proxy is the following:
localhost:/cloudsql/project-name:region:sql-instance-name
It is the same I use in the config file to connect the site to the db.
"Connection Refused" error occurs when an application attempts a TCP connection but there is either no service listening on the target address and port or a firewall rejecting the connection.
First, lets make sure you are connecting on the right port. Run sudo netstat -lntp and look for cloud_sql_proxy. For example you might see
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 71313/cloud_sql_pro
indicating cloud sql is listening on port 3306. If you saw this, you should change the port in your tool to 3306.
If netstat does not show any cloud_sql_proxy line, then it isn't listening on TCP. While TCP isn't always needed for MySQL, it looks like the tool your are using does need it. Make sure you start cloud_sql_proxy with -instances=<INSTANCE_CONNECTION_NAME>=tcp:3306
Second, lets make sure you are connecting on the right address. This should be localhost without :/cloudsql/project-name:region:sql-instance-name after.
If it still doesn't work after those two, use sudo iptables -L to look for firewall rules blocking the traffic. I believe it's unlikely that you have a firewall stopping local traffic, however.
An alternative to using the Cloud SQL Proxy is to connect directly to your instance. To do this:
Find the external IP address of the VM you are running the PHP tool on.
Grant access for that IP address to your SQL instance, with the instructions here
Because MySQL can have different username/password depending on where you connect from, ensure there is a username/password combo for host %. instructions here.
Use the tool, with the username/password from (3), port=3306 and host=the IP address of your SQL instance
When you are done, remove access from the IP address to your Cloud SQL instance.
I want to access machine A which is behind the firewall through a jump host from machine B.
I want to do the same either via ssh keys or via username and password.
What will be the steps and the commands to achieve the same?
The feature is called port forwarding:
ssh -L localport:machine-a-address.domain:remote-port machine-b
Then you can simply use localpott on localhost to access the remote service on machine-a, for example:
telnet localhost localport
I am using apache cloudstack. System VMs are in running state but unable to download system template. when I am login to system VMs through ssh using linked local ip then the it is not able to ping DNS,Management server and host.
check it has the correct management server ip and all routes are proper.
You could try a destroy to recreate the SSVM.