Tunneled webhook is closed after first call about n8n HOT 11 OPEN

are you seeing this for the webhooks that you start using "Test Workflow" or "Listen for test event" via the UI, or also for production webhooks that get created when you activate the workflow?

from n8n.

@netroy I click "Listen for test event" via UI. Env is set on development. Also I set DEBUG mode

from n8n.

@GGG1998 is this for a production environment or is it just a test?

I noticed you mentioned a company network as well, Is it possible that there is a company firewall / proxy that is closing the tunnel connection as I have seen issues in the past where they can sometimes close tunnels if not set to be allowed.

from n8n.

I refer to n8n you cannot be on the company network _if you work at n8n_ because I wanted from you 1:1 chance to reproduce my problem. All I tested on my local computer in my home network.

from n8n.

I click "Listen for test event" via UI
to me this sounds like you are using a webhook test URL, which is valid only for one use.

You need to use the production url for non-testing purposes. More info here.

from n8n.

Still nothing, additionally I'd like to mention that in AWS SNS is status Pending confirmation
Could you tell me in what environment you run n8n?

from n8n.

in AWS SNS is status Pending confirmation

not clear how that's related to this issue. are you using the SNS node?
It'd be helpful if you could share a sample workflow when reporting issues, otherwise we don't have enough context to provide support.

Could you tell me in what environment you run n8n?

We (and our customers) run n8n in lot's of different environments, including AWS.

from n8n.

It's related. SNS


store link to tunneled webhook.

from n8n.

@netroy any idea?

from n8n.

unfortunately I still don't understand the issue. I'll let someone else handle this 🙏🏽

from n8n.

Hey @GGG1998,

I just want to go back to an earlier post...

You can use my docker image and you cannot be on the company network if you work at n8n

Just to clarify, Does this only fail from a company network or do you have the issue when running from your own machine on your own network?

I would also recommend not using the tunnel as we will be removing it soon as there are better options available like Cloudflare and NGROK.

from n8n.