Request node fail when call a webhook on another internal workflow

[lqdominguez]

Describe the issue/error/question

I’m making an http request to a webhook in another workflow in the same n8n instance and I’m getting the error “connect ETIMEDOUT”. When I make a request from out of the n8n instance I get the response instantly.

What is the error message (if any)?

ERROR: UNKNOWN ERROR - check the detailed error for more information

connect ETIMEDOUT

{
“status”:“rejected”,“reason”:{“message”:“connect ETIMEDOUT ”,“name”:“Error”,“stack”:“Error: connect ETIMEDOUT \n at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1278:16)”,“code”:“ETIMEDOUT”}
}

Please share the workflow

This is a test workflow to make the request

This is a test workflow with the webhook

Information on your n8n setup

• n8n version: 0.220.0
• Database you’re using (default: SQLite): SQLite
• Running n8n with the execution process [own(default), main]: default
• Running n8n via [Docker, npm, n8n.cloud, desktop app]: Docker

[Jon]

Hey @lqdominguez,

So my first question is why are you calling the same instance with an http request node and a webhook instead of using the execute workflow option?

The second question is which URL are you using? If you are using the public URL it could be that there is a routing issue so replacing the https://n8n.domain.com with http://localhost:5678 might be the solution there.

[lqdominguez]

So my first question is why are you calling the same instance with an http request node and a webhook instead of using the execute workflow option?

I’m not using the execute workflow option because I’m having problems to test the called workflow when I try to use that trigger.

This solve the problem

The second question is which URL are you using? If you are using the public URL it could be that there is a routing issue so replacing the https://n8n.domain.com with http://localhost:5678 might be the solution there.