ok then i guess ill stick to version 1.42.1 for now till find out about that and Thank you for your patience during the investigation regarding this error @netroy
Iāve updated the branch with a possible workaround. If / when you have time, can you please update the instance, and try one last time please 
PS you might need to run a docker pull n8nio/n8n:enable-keepAlive to update the docker image, since I pushed the changes to the same tag.
1 Like
My current leading theory is this:
Starting node.js 20, requests try to connect to both IPv4 and IPv6 addresses, and use the socket that opens first.
So, this bug exists only for services that resolve their domain to IPv6, but somehow arenāt actually responding to those v6 addresses in a timely manner.
Iāve updated our base docker image to the latest version of node.js 20, so that if this is somehow fixed in there already, the next release should hopefully also fix this.
However if the issue still persists in the next release, Iāll create a quick PR to disable the new socket autoSelectFamily thing, and create a new patch release right away.
1 Like
hi @netroy its already fix on this version Release [email protected] Ā· n8n-io/n8n Ā· GitHub?
I have the same problem, but with the odoo node. It was working smoothly until this morning and out of nowhere it started to time out.
@tridi We upgraded node.js in 1.47.0, but we donāt know if that fixes the issue.
Can you please upgrade and test again?
If the updated node.js does not fix the issue, Iāll cherry-pick the workaround into a PR and get this fixed in a patch release ASAP
hi @netroy sorry for late response, ived testing out new pre release version Release [email protected] Ā· n8n-io/n8n Ā· GitHub and its not fix the problem.
1 Like
New version [email protected] got released which includes the GitHub PR 9860.
2 Likes
Just updated to this version.
Credentials connect fine and http request is able to call the API.
However the telegram node returns this error:
301 - ā\r\n301 Moved Permanently\r\n\r\n
301 Moved Permanently
\r\nnginx/1.18.0\r\n\r\n\r\nā
301 Moved Permanently 301 Moved Permanently nginx/1.18.0
Can you please share a minimal workflow to reproduce this?
Itās also possible that Telegramās IPv6 addresses are doing something weird at an edge location close to you. You could try adding the following env variable to prefer IPv4 : NODEJS_PREFER_IPV4=true
2 Likes
Can you please try running this workflow to see what url telegram is redirecting you to?
This shows me my bots details correctly. Only the telegram node doesnāt work 
Can you share your actual workflow json and how you have n8n deployed? You are getting a message from an nginx server somewhere which wonāt be from us and we have not changed the node so I wonder if maybe you are using a proxy?
Since 1.43.0, Telegram credentials allow settings a custom baseUrl.
Sounds like you have the baseUrl set to some nginx instead of https://api.telegram.org.
1 Like
First of, thanks for responding so quickly to these questions.
Iām running n8n on a docker behind cloudflare. Not using nginx.
You got it right. My url was pointed to http:// instead of https://
Might have left it at that when I was trying to debug why the node wouldnāt work in earlier versions.
Just tested it and it works now.
Once again. Thank you!
2 Likes
Hey everyone, Iāve tried almost everything here, but keep getting the same result.
After adding webhook in workflow and testing it 1 time - everything fine, I am getting 200 code in postman.
The second I stop testing webhook/ close it / deactivate then activate/, or delete and and another one - I am getting 408 in postman.
Actualy I need webhook for pipedrive and Iāve tried to use PipeDrive Trigger - same situation here - first time it triggers and in pipedrive Iāam getting 200 code, second time - 408.
Please,help 
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.