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)
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)
Just wanted to inform you that I’ve created issue in popsicle-transport-http
It seems that the bug was found and was fixed in latest popsicle release!! So I’m waiting for new n8n release to test it out
P.S.: Before fixing there was one comment though about n8n and I feel the need to share it. Maybe it’s still important.
I’ve been having issues with the Outlook node timing out randomly after updating to a recent version (0.100 => 0.116.1) too, don’t know if it’s the same issue though. I have two Outlook nodes in a workflow and only one of them works successfully but the other one throws an error.