Some webhooks get refused with ErrConnection - but Curl works

Questions
1

Describe the problem/error/question

Trouble with n8n incoming webhooks.

I have a vanilla community version set up with Docker. Been working well for a few years. Version 1.36.1

Building a new workflow and struggling with receiving incoming webhook.
I have other workflows receiving incoming webhooks to port 5678

With this workflow. I can receive the webhook when I use the following curl from a remote server

curl --header "Content-Type: application/json"   --request GET   --data '{"name ":"xyz","whatever":"xyz"}'  https://n8n.thebestmashups.com/webhook/snftlabs

HOWEVER I tried to get a webhook from clearbit which failed. So I fired up Postman to test the webhook and this is where it also fails with a Econnrefused error.

Just to confirm I had no silly Iptables rules - Here is the output of iptables -S

-P INPUT ACCEPT
-P FORWARD DROP
-P OUTPUT ACCEPT
-N DOCKER
-N DOCKER-ISOLATION-STAGE-1
-N DOCKER-ISOLATION-STAGE-2
-N DOCKER-USER
-A FORWARD -j DOCKER-USER
-A FORWARD -j DOCKER-ISOLATION-STAGE-1
-A FORWARD -o docker0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -o docker0 -j DOCKER
-A FORWARD -i docker0 ! -o docker0 -j ACCEPT
-A FORWARD -i docker0 -o docker0 -j ACCEPT
-A FORWARD -o br-402fcf3f1d72 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -o br-402fcf3f1d72 -j DOCKER
-A FORWARD -i br-402fcf3f1d72 ! -o br-402fcf3f1d72 -j ACCEPT
-A FORWARD -i br-402fcf3f1d72 -o br-402fcf3f1d72 -j ACCEPT
-A DOCKER -d 172.18.0.2/32 ! -i br-402fcf3f1d72 -o br-402fcf3f1d72 -p tcp -m tcp --dport 5678 -j ACCEPT
-A DOCKER -d 172.18.0.3/32 ! -i br-402fcf3f1d72 -o br-402fcf3f1d72 -p tcp -m tcp --dport 443 -j ACCEPT
-A DOCKER-ISOLATION-STAGE-1 -i docker0 ! -o docker0 -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -i br-402fcf3f1d72 ! -o br-402fcf3f1d72 -j DOCKER-ISOLATION-STAGE-2
-A DOCKER-ISOLATION-STAGE-1 -j RETURN
-A DOCKER-ISOLATION-STAGE-2 -o docker0 -j DROP
-A DOCKER-ISOLATION-STAGE-2 -o br-402fcf3f1d72 -j DROP
-A DOCKER-ISOLATION-STAGE-2 -j RETURN
-A DOCKER-USER -j RETURN

SO I am super confused as to why I receive the curl webhooks but cant get anything in through Postman. I also have other workflows receiving webhooks from such as Alchemy etc.

Any thoughts would be super helpful. I going nuts here

And yes I have tried both on the test URL as well as the production URL - same results

What is the error message (if any)?

My Workspace
No environment
GET
https://n8n.thebestmashups.com:5678/webhook/snftlabs
231
    {
        "name": "Paul item",
        "code": 1
    }

Online
GET https://n8n.thebestmashups.com:5678/webhook/snftlabs
Error: connect ECONNREFUSED 143.244.181.106:5678
Network
agent: "Cloud Agent"
Request Headers
Content-Type: application/json
User-Agent: PostmanRuntime/7.37.3
Accept: */*
Cache-Control: no-cache
Postman-Token: ff01e427-c051-45e5-82b6-f2bfa6ed890b
Host: n8n.thebestmashups.com:5678
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Request Body
    {
        "name": "Paul item",
        "code": 1
    }↵

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.36.1
  • Database (default: SQLite): Yes
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Ubuntu 22.04
2

As I see, the webhook is publicly available on port 443 (as the curl command was sucessful), not on port 5678

1 Like
3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.