Connection Errors since 0.112.0

Hello,

since 0.112.0 we have experiencing connection errors to login.microsoft.com.
Same problems persist with 0.113.0. Though there are no issues with 0.111.0

To reproduce the error … it appears every second time when trying to reauthenticate with Oauth2 credentials (for example Microsoft Outlook API or basic OAUTH2)

The logs show this information


2021-03-29T11:21:21.864+03:00	at TLSSocket.onError (/usr/local/lib/node_modules/n8n/node_modules/popsicle-transport-http/dist/index.js:589:35)

2021-03-29T11:21:21.864+03:00	at Object.onceWrapper (events.js:422:26)

2021-03-29T11:21:21.864+03:00	at TLSSocket.emit (events.js:315:20)

2021-03-29T11:21:21.864+03:00	at emitErrorNT (internal/streams/destroy.js:106:8)

2021-03-29T11:21:21.864+03:00	at emitErrorCloseNT (internal/streams/destroy.js:74:3)

2021-03-29T11:21:21.864+03:00	at processTicksAndRejections (internal/process/task_queues.js:80:21)

2021-03-29T11:21:21.864+03:00	(node:6) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)

What changed?

Hey @Rugia!

There were no changes made to the nodes. Did you try with new credentials?

Hey,

I’ve tried credentials from two different tenants and two different Client ID’s (Azure applications). Same issues persist :frowning:

So downgrading solves the issue? Because then maybe an underlying library changed.

Yes @jan downgrading to 0.111.0 and below solves the issue.
Upgrading to 0.112.0 or 0.113.0 reproduces the issue.

This is quite weird. The Outlook node is working just fine for me with 0.112.0.

Sorry for the slow response… but it’s actually weird because I can reproduce it on two independent installations (docker on-prem and aws ECS).

To reproduce the timeout I’m initiating re-auth / connect.

And every second time I get Timeout
image

So far I understand I’m the only one that is experiencing this kind of problems? :expressionless:

I’ve done some research and it seems that popsicle-transport-http has changed on 2021.03.16 to version 1.1.3 (before n8n 0.112.0 version) https://www.npmjs.com/package/popsicle-transport-http?activeTab=versions

Is it possible to change the popsicle-transport-http module version after n8n deployment?