S3 upload fails

[martinounap]

What happened?

We are using Google Cloud Storage, but with HMAC and s3 compatible.
After uograding to -r3 we can not upload files, because signature mismatch.

Log: {"$fault":"client","$metadata":{"httpStatusCode":403},"Code":"SignatureDoesNotMatch","Details":"The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.","level":"error","message":"Invalid argument.","name":"SignatureDoesNotMatch","stack":"SignatureDoesNotMatch: Invalid argument.\n    at throwDefaultError (/app/node_modules/@aws-sdk/client-s3/node_modules/@smithy/smithy-client/dist-cjs/index.js:867:20)\n    at /app/node_modules/@aws-sdk/client-s3/node_modules/@smithy/smithy-client/dist-cjs/in...","timestamp":"2025-09-08T08:08:22.730Z"}

Google secret and access key are correct.

Version Information

ghcr.io/danny-avila/librechat v0.8.0-rc3 fdaddca5d75c 13 days ago 1.57GB
ghcr.io/danny-avila/librechat v0.8.0-rc2 78a279684768 3 weeks ago 1.17GB
ghcr.io/danny-avila/librechat-rag-api-dev-lite v0.6.0 fdceac10490b 4 weeks ago 1.48GB
ghcr.io/danny-avila/librechat v0.8.0-rc1 25d757180cb4 4 weeks ago 1.17GB
ghcr.io/virtuos/librechat_exporter main 3012a75299b4 2 months ago 283MB

Steps to Reproduce

1. Connect to Google Cloud Storage with HMAC
2. try to upload file
3. you should get error message

What browsers are you seeing the problem on?

No response

Relevant log output

{"$fault":"client","$metadata":{"httpStatusCode":403},"Code":"SignatureDoesNotMatch","Details":"The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.","level":"error","message":"Invalid argument.","name":"SignatureDoesNotMatch","stack":"SignatureDoesNotMatch: Invalid argument.\n    at throwDefaultError (/app/node_modules/@aws-sdk/client-s3/node_modules/@smithy/smithy-client/dist-cjs/index.js:867:20)\n    at /app/node_modules/@aws-sdk/client-s3/node_modules/@smithy/smithy-client/dist-cjs/in...","timestamp":"2025-09-08T08:08:22.730Z"}

Screenshots

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[martinounap]

Strange behaviour. Image upload is working. But upload for files for RAG is not working.

[martinounap]

I found solution. It seems that fileStrategy: "s3" did not work. But new config did woork:

fileStrategy:
  avatar: "s3"        # Storage for user/agent avatar images
  image: "s3"   # Storage for uploaded images in chats
  document: "s3"

[martinounap]

I was wrong, this kind of config broke config reading.

{"level":"error","message":"Invalid custom config file at /app/librechat_custom.yaml:\n{\n  \"issues\": [\n    {\n      \"expected\": \"'local' | 'firebase' | 'azure' | 'azure_blob' | 'openai' | 's3' | 'vectordb' | 'execute_code' | 'mistral_ocr' | 'azure_mistral_ocr' | 'vertexai_mistral_ocr'...","timestamp":"2025-09-08T12:33:10.208Z"}

So i bleive, I need to wait next version to use this kind of config? @danny-avila

[martinounap]

Reopen until @danny-avila answer. Right now it seems that it is impossible to use s3 (or like) solution with RAG in -r3 version. New stile config is also not supported yet.

[danny-avila]

Both image and file uploads are working for me via S3 (not GCS) using just the following:

fileStrategy: "s3"

Double-check your S3 credentials:

## S3
AWS_ACCESS_KEY_ID=access_key
AWS_SECRET_ACCESS_KEY=secret_access_key
AWS_REGION=your_region
AWS_BUCKET_NAME=your_bucket_name

[martinounap]

Strange, when I am using fileStrategy: "s3" then image upload works perfect but file upload is not working.
When it is possible to use config like tihis:

fileStrategy:
  avatar: "s3"        # Storage for user/agent avatar images
  image: "s3"   # Storage for uploaded images in chats
  document: "local"

Then I believe I can forgot this problem, because after RAG is done, temp file will be deleted anyway.
But it is strange, that image upload works and document upload fails with error "SignatureDoesNotMatch". I tried to debug it, but right now I finished with conclusion, that it is magic for me :D and it is easier to use local file storage right now.