499 - Client Closed Request when calling another n8n workflow via http request

[Giovanni_Segar]

I’m on n8n cloud.

I’ve got two workflows: one “helper” workflow which receives some delivery dates and calculates a ship date from it and returns a response, and another which calls this workflow to get the ship date and do something with it.

A new issue that started today is that the primary workflow gets a “499 - Client Closed Request” error when calling the helper workflow.

But the helper workflow runs in ~2 seconds and is successful with no errors:

I made sure to set the timeout to 50 seconds so it’s not that.

The behavior is unpredictable, sometimes it works and sometimes it doesn’t.

It has been working for the past few days with no problem, and only started randomly having this issue in the past 12 hours or so.

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

[steph]

I have the same problem since this morning, and also it seems unpredictable.

To me it happens with HTTP node, in many workflows, even when workflow is not called by another one.

• n8n version: 1.36.1
• Database : postgresql
• Running n8n via (Docker, npm, n8n cloud, desktop app): docker
• Operating system: Ubuntu 22.04.4 LTS (GNU/Linux 5.15.0-102-generic x86_64)

[Jon]

@Giovanni_Segar this is an issue we are aware of on Cloud and we are fixing it at the moment.

[netroy]

This should be resolved now.
The issue was that when we upgraded our reverse-proxy earlier today, it changed the default timeout for connections to 5 seconds. We have also updated the configuration to remove the implicit timeout, as it used to be.

[steph]

@netroy I have the same problem since this morning, and I am on self-hosted docker. The problem is still happening now. Does it mean there is no connection at all with what you describe?

Edit : to be more precise, I am not certain it started this morning, but it was reported by a client this morning, and it worked fine recently.

[Kienou_Nestor]

Hi everyone!
One of our client is getting the same error. Sometimes it’s fine.
But on our side we are getting this since 10 days. Please help us resolve the problem!

[netroy]

@Kienou_Nestor This issue is related to the 499s (and other connection timeouts) that started happening earlier today.

Since the issue you mention is there since 10 days, it’s likely a completely different issue.
Can you please start a new topic, fill up the template, and add any additional info that might help us reproduce the issue?
Without all that information, we don’t even know what the issue is. It’s very unlikely that we can fix a bug without first understanding the bug.