power
February 24, 2025, 9:30pm
1
Hello!
I’m using a pre-signed URL to upload an MP3 file to a vendor’s AWS S3 bucket.
A CURL PUT request from the terminal works flawlessly.
However, the same request mimicked in an n8n HTTP Request node fails every time — with a SignatureDoesNotMatch error.
To boot, the same PUT request sent from my Insomnia client also fails with the same error.
NOTE: Mac Terminal (zsh) needed the signed URL to be single-quoted. HTTP Request fails when I try that in n8n, indicating “Invalid URL.”
Any thoughts on what’s going on here?
n8n
February 24, 2025, 9:30pm
2
It looks like your topic is missing some important information. Could you provide the following if applicable.
n8n version:
Database (default: SQLite):
n8n EXECUTIONS_PROCESS setting (default: own, main):
Running n8n via (Docker, npm, n8n cloud, desktop app):
Operating system:
solomon
February 24, 2025, 10:39pm
3
Hey @power ,
Is that part of the authentication required by the S3 bucket?
If yes, then maybe you could solve the problem by creating the correct Credential for AWS S3.
If not, can you please share your workflow JSON code?
Just copy and paste your nodes into a code block:
like this
power
February 25, 2025, 12:24am
4
Thanks, @solomon .
The URL itself is where the authentication lives. It’s an expiring link. There’s no other authentication or credentialing involved.
The CURL call passes only the signed URL and the file path. No errors there.
But doing (essentially) the same thing via HTTP Request fails.
I’ll share my workflow as soon as I’m back at my keyboard.
1 Like
solomon
February 25, 2025, 1:14am
5
Alright. If you can send me an example token in the URL, I’ll try to validate here on my end.
It doesn’t have to be a current working token. It can be an expired one.
system
Closed
May 26, 2025, 3:00am
7
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.