S3 bug in 2.10.x - 2.11.0

Describe the problem/error/question

There seems to be a bug in 2.10.x to 2.11. Uploading a file o S3 always returns:

Bad request - please check your parameters

EntityTooSmallYour proposed upload is smaller than the minimum allowed“

No matter how big the binary is. Tested < 1mb & > 10mb

What is the error message (if any)?

EntityTooSmallYour proposed upload is smaller than the minimum allowed

Information on your n8n setup

  • n8n version: 2.10.2 - 2.11.0
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm
  • Operating system: ec2
1 Like

Hi @Kool_Baudrillard Consider upgrading your n8n instance to the latest stable version, that would work. (You can also downgrade to the n8n version if it was working in some builds below 2.8.x.)

This looks like a regression in the multipart upload logic they added to the S3 node, the EntityTooSmall error means S3 is rejecting individual upload chunks that are under 5MB which shouldn’t be happening for normal file sizes. I’d open a GitHub issue at GitHub · Where software is built if one doesn’t already exist for this, and in the meantime rolling back to whatever version you were on before 2.10.x should get you unblocked.

This looks like a regression in how the S3 node handles multipart uploads, it’s splitting files into chunks smaller than S3’s 5MB minimum part size. I’d roll back to 2.9.x as a workaround and open a GitHub issue at GitHub · Where software is built if there isn’t one already so the team can get a fix in.

Yeah this is a regression in the multipart upload logic, S3 requires each part of a multipart upload to be at least 5MB (except the last chunk) and it looks like something in 2.10.x broke the chunking so it’s sending parts under that threshold which triggers EntityTooSmall regardless of actual file size. I’d file a GitHub issue at GitHub · Where software is built if there isn’t one already so the team can track it, and in the meantime rolling back to something pre-2.10 where the upload logic was working correctly is probably your best move.

When was this introduced?