Can't use S3 Sdk - SignatureDoesNotMatch #495
Comments
|
Hello, https://github.com/supabase/storage/blob/master/docker-compose.yml#L46-L47 Let me know if that work |
If you check the |
|
are you running storage behind a reverse proxy? If yes, you'd need to add the |
|
If you are not, don't set the S3_PREFIX_URL, and the URL you are using to connect to storage shouldn't contain the const s3Client = new S3Client({
logger: console,
forcePathStyle: true,
region: "stub",
endpoint: "http://localhost:5000/s3",
// endpoint: "http://localhost:9000",
credentials: {
accessKeyId: "supa-storage",
secretAccessKey: "secret1234",
},
}); |
I'm running the default Following your instructions I'd added the follwoing to my # ...
S3_PROTOCOL_PREFIX: /storage/v1 # Added
# ...
S3_PROTOCOL_ACCESS_KEY_ID: supa-storage
S3_PROTOCOL_ACCESS_KEY_SECRET: secret1234
AWS_ACCESS_KEY_ID: supa-storage
AWS_SECRET_ACCESS_KEY: secret1234and then request with: const s3Client = new S3Client({
logger: console,
forcePathStyle: true,
region: "stub",
endpoint: "http://localhost:5000/storage/v1/s3",
credentials: {
accessKeyId: "supa-storage",
secretAccessKey: "secret1234",
},
});
const createBucketRequest = new CreateBucketCommand({
Bucket: "test-bucket",
ACL: "public-read",
});But still got the same error. Storage container logs |
|
Right! if you use kong you'll need to add this snippet in the storage route: |
|
Just be more specific, you'll need to update this line on the supabase repo you have linked: https://github.com/supabase/supabase/blob/master/docker/volumes/api/kong.yml#L64 The host will be the host you are accessing Kong, in development will be @kallebysantos let me know if this works for you, I'm quite confident it will since we use the same setup on the supabase cli |
So I need to update both: I'd follow the other steps that you provide but it didn't work, I'll try to redo everything again in a new fresh installation of supabase. Thank you, I'll let you know 🙏 I just don't have much time for now, a guy in my team decided to not move on with supabase in this project 😭😭 and I need to redo everything that I spend a whole month in another stack. But this |
It will work since we use the same setup on the supabase cli. I'll be closing this issue for now, however if you need need any more help on this, please feel free to comment below and I can re-open in case. |
|
Hey @fenos I'm self-hosting, and tried to follow the steps you wrote above. Am seeing the Standard and Resumable uploads work. At one point I was getting the following error:
But that seems to have been my mistake with restarting the containers properly, because I'm not seeing this anymore. Now I get the Any pointers on what I could be doing wrong? Is there anything more I can share that could help? Storage configThese are the environment variables for the storage container: Kong configMy kong config for the storage-v1 path is as follows: Notice the Python Boto3Example of how I'm doing the upload from a client application with Python and boto3. Couldn't find anything about using Python in the docs, so lots of guessing and trying. |
Bug report
Describe the bug
I'm trying to use
S3 Sdkto perform operations on Supabase Storage. But everyCommandthat I try simple doesn't works and result in403: SignatureDoesNotMatcherror. But if I call to Minio endpoint instead it works.To Reproduce
Run
docker-compose.s3.ymlwith the following:code
Then I copy the following code from supabase storage tests:
Current behaviour
Application Logs:
Supabase Storage Logs:
{ "level": 40, "time": "2024-05-31T09:22:39.510Z", "pid": 1, "hostname": "eb7efc6421e9", "reqId": "req-2", "tenantId": "stub", "project": "stub", "type": "request", "req": { "region": "stub", "traceId": "req-2", "method": "PUT", "url": "/s3/a25af482-0a92-4036-aef3-1a9125389070/", "headers": { "host": "storage:5000", "x_forwarded_proto": "http", "x_forwarded_host": "localhost", "x_forwarded_port": "8000", "x_real_ip": "172.18.0.1", "content_length": "186", "content_type": "application/xml", "user_agent": "aws-sdk-js/3.583.0 ua/2.0 os/linux#5.15.146.1-microsoft-standard-WSL2 lang/js md/nodejs#20.11.1 api/s3#3.583.0", "accept": "*/*" }, "hostname": "storage:5000", "remoteAddress": "172.18.0.13", "remotePort": 55906 }, "res": { "statusCode": 403, "headers": { "content_type": "application/xml; charset=utf-8", "content_length": "293" } }, "responseTime": 7.990687999874353, "error": { "raw": "{\"metadata\":{},\"code\":\"SignatureDoesNotMatch\",\"httpStatusCode\":403,\"userStatusCode\":400}", "name": "Error", "message": "The request signature we calculated does not match the signature you provided. Check your key and signing method.", "stack": "Error: The request signature we calculated does not match the signature you provided. Check your key and signing method.\n at Object.SignatureDoesNotMatch (/app/dist/storage/errors.js:107:41)\n at Object.<anonymous> (/app/dist/http/plugins/signature-v4.js:36:36)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)" }, "resources": [ "/a25af482-0a92-4036-aef3-1a9125389070" ], "msg": "stub | PUT | 403 | 172.18.0.13 | req-2 | /s3/a25af482-0a92-4036-aef3-1a9125389070/ | aws-sdk-js/3.583.0 ua/2.0 os/linux#5.15.146.1-microsoft-standard-WSL2 lang/js md/nodejs#20.11.1 api/s3#3.583.0" }Expected behavior - Calling :9000 (Minio)
Application Logs:
Minio dashboard:
System information
Additional context
In the example provide I use the
CreateBucketCommandbut the same occours when I trying to upload Multipart documents, like the following snippet copied fromSupabase docs:Uploading to Supabase Storage with S3Client
The text was updated successfully, but these errors were encountered: