That looks like it could be a network issue or possibly some kind of protocol mismatch. I would start by using the latest version of n8n and see if that resolves anything, You mentioned it recently started showing this message so it would be handy to know what has changed as well, if it is nothing on your side then it could be a change on the service you are using.
Hi @Jon Thanks for your thoughts on this. Latest version did not solve the issue for me. I’ll investigate the network side of things both from server and client side and share my findings.
Hi @Jon, It was a issue with the server side I was not in my orgs VPC and and didn’t had a static IP for my service. The requests were Tarpitted causing a timeout on my end. I have bonded a outbound static IP and that solved the issue. No issue with n8n!!