For some reason connecting to a setup monetdb server via
mapi_connect("localhost", 50000, "monetdb", "monetdb", "sql", "demo");
works,
however,
mapi_connect("xxx.xxx.xxx.xxx", 50000, "monetdb", "monetdb", "sql", "demo");
Doesn't work.
I've checked that port 50000 is open, and that the service is up and running.
What am I missing?
Figured it out, the issue was with Port Forwarding in my VirtualBox settings for my Centos VM. For anyone with similar issue, just add a port forwarding rule, in my case it was for port 50000 (which is what my monetdb server runs on). Good luck.
Related
I have a small gcp instance running elasticsearch (on port 9200) and cerebro (on port 9000). I have created firewall rules allowing connection to those 2 ports.
From my workstation I can access "http://instance_external_ip:9000" and I can get into the cerebro UI.
But if I try to curl "http://instance_external_ip:9200" from my workstation's CL I get a 'Connection refused'.
Elasticsearch is clearly running, since I can curl it from within the instance at localhost:9200, and I can access it via cerebro on my workstation.
Thanks for your help.
You can check if the Elasticsearch application is listening on port 9200 using netstat command and adding the atup options to show the TCP and UDP connexions, all sockets and the PID of the process:
netstat -atup
Check if the Firewall Rules are correctly configured for ingress connections, to the related port and if it’s correctly applied on the network that your instance is running.
I have hosted web application (developed in PHP) on Amazon EC2 micro instance. As per default setting, i can access 80, 22, 443 and 3306 ports from remote locations means from Home(terminal window) using telnet command.
I want to open another custom TCP port XXXXX. I have added that port in Security Group. when i am trying to connect that port through telnet command it is always show "Connection refused".
I have been trying to solve this issue for 3 days but could not get successful solution.
Help would be really appreciated.
Thanks
Adding a port in security group (inbound) ensures that the port can be accessed from outside. Please check following
Is the port open for anywhere (0.0.0.0/0) or for a custom IP. If for custom IP, please check the IP of your machine (search 'what is my ip' on google).
Is there any application listening on the port on EC2 machine.
I am having difficulty getting Confluence running on windows server 2012 on port 80. (the machine in hosted in Azure which is why I need to run it on port 80 (i dont have access to other ports from where I am trying to use this)).
I believe something must be running on port 80 , though i did a netstat -y and didnt see anything.
I think its IIS any idea how I should kill that or what else could be causing confluence to not run on port 80?
*confluence works find on say port 8090 but i need to run it on port 80.
mind you I cant get confluence to run on port 80 on the local instance of windows server, never mind accessing it from another location thus i dont think this has anything to do with azure
running a
netstat -abn
shows nothing running on port 80. Im still not sure why I cant get confluence to work locally on port 80.
A virtual machine in Azure is not directly public accessible. You need to configure endpoints in the cloudservice (which acts as a loadbalancer).
So for instance you can configure a public endpoint port 80 on the cloudservice to point to your VM port 8090. See http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-set-up-endpoints/ for more information.
If the Endpoint is open on Azure to the VM then my advice would be to check the firewall settings on the host. Typically most ports are shut unless they are explicitly opened by installing a feature like IIS (windows web server).
I set up Cassandra on EC2 according to this: http://www.datastax.com/docs/datastax_enterprise2.2/install/install_dse_ami
All is well, and it's all up and running, including OpsCenter. For the time being, I have a completely open (0.0.0.0/0) security policy. I'll fiddle with that once I can finally connect remotely.
The problem, I'm told, is that our corporate firewall blocks almost all ports, save for 22, 80, 8080, and 8888. Thus, when I try to connect to Cassandra locally: e:\cassandra\bin\cassandra-cli -host ec2-X-X-X-X.us-east-1.compute.amazonaws.com -port 9160
I get the error:
org.apache.thrift.transport.TTransportException: java.net.ConnectException: Connection refused: connect
Given that I cant open any additional ports in my corporate firewall, what can I do to connect to Cassandra? Can I tell it to allow connections on 8080 instead?
It sounds like you are having trouble connecting from your machine to the Cassandra machine due to the corporate firewall. There are a couple of solutions
Connect to machine via ssh first
You could connect to the EC2 machine and connect from there.
Change the thrift port
You certainly could change the thrift port in the cassandra.yaml file, but make sure you change it in the opscenterd.conf also. Realize that if something else is running on 8080, then this probably will not work.
You could also look into using the DataStax DevCenter too, which would help keep things behind the firewall. This is in alpha, but it may help your situation.
I will be building a server/client software on Windows, where many machines need to communicate with a Postresql database running on the server. This is C++ software so I will use libpq to connect to the database.
If I do this, will there be issues with the firewall? I'd like to make configuration as easy as possible and not have users open up firewall ports or disable their firewall.
If I do need to open up firewall ports, can I use WCF to get around the issue? Basically send a command to the server using WCF, run the postgresql command locally, and get the result back (I have never used WCF but understand that it can communication using HTTP port 80).
PostgreSQL typically listens on port 5432, which is not open by default in the Windows firewall. But the only machine where the firewall would need to be re-configured is the one where PostgreSQL is running. If you have many client machines, none of them should require firewall changes (unless they have restrictions on outbound traffic, which is rare).
Hope this helps.
You can also configure SSL connections to ensure better security.