S3 StorageGrid not able to Connect. Last working with 30.0.2

ℹ️ Support
, , , ,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 33.0.3
  • Operating system and version (e.g., Ubuntu 24.04):
      • Ubuntu 24.04
  • Web server and version (e.g, Apache 2.4.25):
    • replace me
  • PHP version (e.g, 8.3):
    • 8.3
  • Is this the first time you’ve seen this error? (Yes / No):
    • No
  • When did this problem seem to first start?
    • after update from 30.0.2 to 31.0.14
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Bare Metal
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

After updating from version 30.0.2, I was not able since to connect to our onprem S3-compatible storage (StorageGrid) (first updatet to 31.0.14, now to 33.0.3).

Before the update I was able to connect and use different s3 buckets by making use of the external_file app and access-key authentication.

  • If I now make use of “v2 legacy auth”, I am able to connect and test the connection sucessfully in the administration menu, but I am not able to list files in the explorer: 
    • AWS HTTP error: SignatureDoesNotMatch (client): The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method
  • If I make use of v4 auth, I am not even able to connect, since I get log errors indicating that some headers are missing (x-amz-user-agent) 
    • AccessDenied (client): V4 authentication signed header not found: x-amz-user-agent

I cross-checked with a native AWS S3 bucket an can confirm, that those connections and buckets still work fine.

I double checked credentials and rights on the S3 storage (even though nothing changed),

Version 30.0.2 was the last version that worked completely fine, and rolling back to that version still works today - so nothing changed or broke at the onprem-S3 end.

Are there any ideas, what could be the root cause or how to find any workaround?

2

Signatures are very sensitive to values such as the region, even if you don’t think you’re using it, since they are computed independently on the client versus server-side. The AWS SDK makes some assumptions about the defaults too and there have been some differences over time too IIRC.

You may need to set it to us-east-1 IIRC

3

Hey, thanks for reaching out.

Unfortunately, that does not solve the problem and the error messages are staying exactly the same, no matter which region is set.