my question is: why I curl to another port curl in response show this massage that said Connection refused in port 50497enter image description here
Related
After setting up elasticsearch and kibana, I installed curl.
I tried running this command on terminal:
curl -X GET https://localhost:9200
And it is giving this error.
curl: (7) Failed to connect to localhost port 9200 after 6 ms: Couldn't connect to server
Does anyone know how to resolve this issue?
I am trying to connect nuxeo to elasticsearch 6 with port 9300, but the connection is refused.
When I run the curl -XGET 'localhost: 9300' command,
I got the error message:
curl: (7) Failed to connect to localhost port 9300: Connection refused.
Could you help me to solve this problem?
try it , elastic uses 9200 port for API gateway
curl http://localhost:9200
I'm trying to access elasticsearch, not from the host machine, however I get connection refused error.
What I tried:
telnet ip_address 9200
result was:
connect to address ip_address: Connection refused
telnet: Unable to connect to remote host
changing the elasticsearch.yml file. I changed host field to 0.0.0.0 and also tried the actual ip of the host machine, but it didn't help, I still got the error that connenction was refused.
Can you suggest what else can I try to solve this problem?
I am playing with Kubernetes on https://labs.play-with-k8s.com.
I tried to use the kubectl proxy following the instructions in Kubernete's website.
On the Master node (192.168.0.13) I ran: kubectl proxy --port=8080:
[node1 ~]$ kubectl proxy --port=8080
Starting to serve on 127.0.0.1:8080
On the Worker node I ran curl -v http://192.168.0.13:8080 and it failed:
[node2 ~]$ curl -v http://192.168.0.13:8080
* About to connect() to 192.168.0.13 port 8080 (#0)
* Trying 192.168.0.13...
* Connection refused
* Failed connect to 192.168.0.13:8080; Connection refused
* Closing connection 0
curl: (7) Failed connect to 192.168.0.13:8080; Connection refused
Any idea why the connection is refused ?
Starting to serve on 127.0.0.1:8080
As shown in the message it emits on startup, that is because kubectl proxy only listens on localhost (i.e. 127.0.0.1), unless you instruct it otherwise:
kubectl proxy --address=0.0.0.0 --accept-hosts='.*'
and that --accept-hosts business is a regular expression for hosts (presumably Referer headers? DNS lookups?) from which kubectl will accept connections, and .* is a regex that matches every string including the empty ones.
I have Vidalia installed, set up Chrome to use port 8118 for the proxy and I've checked my connection through https://check.torproject.org/ but I'm having difficulties getting this work with the command-line tool cURL. This is what I try:
C:\>curl -v --proxy localhost::9050 http://google.com
* About to connect() to proxy localhost port 0 (#0)
* Failed to connect to ↕: Address not available
* No error
* Trying 127.0.0.1... Failed to connect to 127.0.0.1: Address not available
* No error
* couldn't connect to host
* Closing connection #0
curl: (7) Failed to connect to ↕: Address not available
Solved:
curl -v --socks4a localhost:9050 http://check.torproject.org/
Use --socks5 (two dashes). -socks5 is not a valid parameter for curl, so curl is interpreting it as a hostname.
Turns out this entire mess was just syntax problems. A proper command is here:
curl -v --socks4a localhost:9050 http://check.torproject.org/
With TWO dashes before socks4a and ONE colon before the port.
More updated response using socks5.
curl -v --socks5 localhost:9150 http://check.torproject.org/
So, using port 9150 for socks 5.