Warning: Connection Reset Issue in [4.9.0] which is n8n 2.10.2

[paramedicspecialist]

I noticed a similar issue today after updating to 4.9.0 with one of our n8n workflows that posts binary files to StirlingPDF through the HTTP Request node.

The application logs for n8n show the following error:

Mar 04 13:33:02 Unable to calculate form data length
Mar 04 13:33:02 data should be a string, Buffer or Uint8Array

[joseph]

Not seeing anything in the changelog - https://github.com/n8n-io/n8n/releases . Maybe fixed in 2.10.3 ? But nothing related to this.

[joseph]

@paramedicspecialist I think yours is related to https://github.com/n8n-io/n8n/pull/25807 . The error messages match.

[umnz]

Please note this error persists into the latest version of n8n.

Specifically, I have a sub workflow that is executed that uses an HTTP request to upload files to a third party service. There are a lot of changes between 2.9.4 (working) and 2.10.2 (breaks). I'll continue to investigate and report back if I find anything.

https://github.com/n8n-io/n8n/issues/26748

[umnz]

@girish @Joseph n8n team are claiming the issue could be with changes made by Cloudron between 2.9.4 and above. Can you guys look into this?

There are multiple people claiming that sending binaries via multi-part-forms breaks after upgrading from 2.9.4 - but I don't know if they're using Cloudron.

Here's an example of someone getting the same error sending a multi-part form using the Open AI file upload:
https://github.com/n8n-io/n8n/issues/26777

Other references to connection issues when uploading files:
https://github.com/n8n-io/n8n/issues/26746
https://github.com/n8n-io/n8n/issues/26606
https://github.com/n8n-io/n8n/issues/25567

[zigmasdirigeant]

Same issue here. Workflow downloads audio from some of our tools and uploads to Azure OpenAI Whisper via multipart form. Azure logs confirm requestLength: 0 on every request. Container logs show the same "Unable to calculate form data length / data should be a string, Buffer, or Uint8Array" errors. Can Cloudron roll back to 4.8.2 or push a patched version? OR what's the plan here?
This broke 5 different workflows and things inside my whole enviroment, not critical, but data has been lost in this.

[joseph]

Just to update: we can reproduce this and are debugging this .

[james]

Hello @n8n users

@brutalbirdie debugged this issue and found the issue.
https://github.com/n8n-io/n8n/issues/26748#issuecomment-4031286237

We will update the Cloudron N8N app soon to fix this issue.

[umnz]

@James @brutalbirdie @Joseph

Much appreciated team.

[girish]

@umnz @paramedicspecialist I pushed a new package that does not use npm anymore and uses the upstream docker image. Can you please check?