Alll good team, thanks!!
Works great! Thank you kindly!
n8n:
image: docker.n8n.io/n8nio/n8n:1.76.0
I’m on n8n cloud, I cannot upgrade but getting the same error. What should I do?
this is fixed in the latest versions. Are you not able to run the latest version on cloud? Or did you mean you are not on cloud.
Regardless, the new versions should have this issue fixed
I am using 1.76.1, and I am receiving the same error. I am using the cloud version. Is there a permanent fix yet?
@John_Dixon can you please share more details? and please share workflow where you can reliably reproduce this issue.
This issue is not fixed in 1.85.4 - I have a long running AI Agent query and eventually this things breaks the exact same way as originally reported. Is there a permanent fix to this ?
The code currently auto-closes any SSH tunnel connections that seem like they have been idle for over 5 minutes. The 5 minutes check is hard-coded.
We could make that configurable, and let you configure it to a duration that suits your needs.
Would that work for you?
Adding the idle timeout customization here.
Once this is released, you should be able to set N8N_SSH_TUNNEL_IDLE_TIMEOUT to a longer duration, to prevent the SSH tunnel from closing on such long-running queries.
You are a star ! Thank you so much !
New version n8n@1.89.0 got released which includes the GitHub PR 14522.
Hi, I am still getting this error. I am on n8n version 1.91.3
if u’d like i can try test with ure workflow, u can share like this, or just a basic version of it with the error nodes,
once u click the code button, just hit paste,.
I think we got the same issue with the pool because of the hardwritten ttl here : n8n/packages/nodes-base/utils/connection-pool-manager.ts at master · n8n-io/n8n · GitHub
when 2 calls are made in more than 5 minutes we got a pool error.
Whould it be possible to add the same configuration mechanism ? Or do you see some workaround ?
Thx