curl: (7) Failed to connect to localhost port 443: Connection refused - webhooks

#curl -k https://localhost/api/v1/webhooks/sample -d '{"foo": "bar", "name": "st2"}' -H 'Content-Type: application/json' -H 'X-Auth-Token: put_token_here'
curl: (7) Failed to connect to localhost port 443: Connection refused

This most likely means that there is nothing listening.
Are you sure that the port is 443? It's common to run at a different port when developing and running websites/apis in debug. The port could be 44301, for example.

Related

curl (56) Recv failure: Connection reset by peer with a simple docker run

Yesterday this image was working fine.
But from today i have always the same error.
Here the command :
sudo docker run --name matter -d --publish 8065:8065 --add-host dockerhost:127.0.0.1 mattermost/mattermost-preview
When i curl :
curl: (56) Recv failure: Connexion ré-initialisée par le correspondant
English : curl (56) Recv failure: Connection reset by peer with a
simple docker run
Sometimes when i wait i can access to my localhost.
When i i do this :
sudo netstat -tulpn | grep LISTEN
I have this :
tcp6 0 0 :::8065 :::*
LISTEN 25772/docker-proxy
I don't understand this error :/
I am on Linux Ubuntu 18
The server takes a while to get ready to accept requests.
If you do
sudo docker logs matter
you can see the output of the server. Wait until you see a message like this
{"level":"info","ts":1624436113.1993275,"caller":"app/server.go:1226","msg":"Server
is listening on [::]:8065","address":"[::]:8065"}
before you start making requests.

Errors seen when setting up logspout in Hyperledger fabric 2.2

Following steps described here to setup logspout:
https://hyperledger-fabric.readthedocs.io/en/release-2.2/deploy_chaincode.html
Running this produces below errors:
./monitordocker.sh net_test
Starting monitoring on all containers on the network net_test
xxxx
docker: Error response from daemon: network net_test not found.
curl: (7) Failed to connect to 127.0.0.1 port 8000: Connection refused
xxx#xxxx:/home/fabric/fabric-samples/test-network#
xxx#xxxx:/home/fabric/fabric-samples/test-network# ./monitordocker.sh
Starting monitoring on all containers on the network basicnetwork_basic
xxxx
docker: Error response from daemon: network basicnetwork_basic not found.
curl: (7) Failed to connect to 127.0.0.1 port 8000: Connection refused
xxx#xxxx:/home/fabric/fabric-samples/test-network#
xxxx#xxxx:/home/fabric/fabric-samples/test-network# ./monitordocker.sh net_basic
Starting monitoring on all containers on the network net_basic
xxxx
docker: Error response from daemon: network net_basic not found.
curl: (7) Failed to connect to 127.0.0.1 port 8000: Connection refused
Few questions:
there is no process running in default port 8000. So connection refused error is expected. Do we need to use any other port ?
what is the name of the network to be given when running monitordocker.sh ?
Any other troubleshooting info is appreciated.
Ok, found the issue. The network name is fabric_test. So I issued command like
./monitordocker.sh fabric_test
This resolved the problem.

curl: (7) Can't complete SOCKS5 connection to 0.0.0.0.0:6677. (8)

curl -x socks5://uesr:pw#ip:prot https://drive.google.com/u/0/get_video_info?docid=1uGgYyuU_-s-n68kulQ42p4gJt1RcsmUO
curl: (7) Can't complete SOCKS5 connection to 0.0.0.0.0:6677. (8)
Please help me

unable to connect to management.azure.com from azure app service

I have an azure app service which I need to communicate to management.azure.com and I am getting below error.
Curl query I am executing from appservice kudu url is:
curl -v -X GET -H "Content-Type:application/json" -H "Authorization: Bearer XXXXXXXXXX" https://management.azure.com/subscriptions/{AuthToken}/resourceGroups/{ResourceGroup}/providers/Microsoft.Web/sites/{appservicename}/slots?api-version=2019-08-01
About to connect() to management.azure.com port 443 (#0) Trying 13.86.219.80... Connection timed out Failed connect to management.azure.com:443; Connection timed out Closing connection 0curl: (7) Failed connect to management.azure.com:443; Connection timed out.
Where as I am able to communicate https://login.microsoftonline.com and get the auth token where as getting timed out for management.azure.com.
Do we have any restrictions in communicating to management.azure.com in appservices settings or firewall settings? We have enabled the proxy and able to communicate to external sites. Only facing connectivity to management.azure.com.
Can I get any help?

Unable to connect port 8080 in presto-cli

presto:tpch> show tables;
Error running command: Server refused connection: http://localhost:8080/v1/statement
presto:tpch> exit
I have tried adding 8080 in firewall but that is not working.

Resources