[bug] not able to set S3 region

[vickailiu]

Description of the bug

not able to set S3 region

Step by step instructions to reproduce the bug

• Click on "checkbox" before and after "Advanced"
• Copy region ("ap-southeast-1" in my case) into "region"
• When I refresh the page, the setting is not reflected to be set.

I've checked the API call: /admin/api/config after making the configuration. The post request seems does not send the "region" in the request. I've tried to add it in, but seems not working as well.

Can you replicate that error from the demo?

Observed behavior

Expected behavior

[WGandy]

I'm running into what appears to be the same issue. I'm trying to set this up with an S3 style object storage called Garage. It requires the region be set to "garage". I set this in the advanced section and it does appear to connect to the service and create folders. But if I create a document with Filestash, I get an error when trying to save it. A similar error when trying to drag a file for upload with Filestash.

AuthorizationHeaderMalformed.

I'm seeing the default region (us-east-1) which would be incorrect. And I believe this error is what we can expect when the region is incorrect.

But I'm also wondering if there is an issue with the format for requests. Minio and Garage both use path style requests (at least by default).

[mickael-kerjean]

If someone can send me a testing account I will look into it: [email protected]

[mickael-kerjean]

I have never got any testing account to replicate this. I'm closing the ticket until somebody is willing to send me what I need to provide a fix.

[nicolasbri]

One of my users has experienced the same issue: bucketregionerror, the bucket is not in US-east-1.... code301. He created a folder within the bucket and got the error when uploading to the folder. He could upload fine to parent folder. I tried on my side and could upload without errors on the folder, whch makes me think it is a local issue. After having a look on Google, user experience this issue when using Terraform (infrastructure from code) and the solution is to delete the .terraform file. Could there be a similar temporary file created locally by Filestash?

[mickael-kerjean]

There's temp file only whenever using things like GIT for which there's no other choices but that's not the case with S3 where there is no such temp file. To understand what's going on, I'd need to have a testing account from which I could replicate this

[nicolasbri]

Thanks for your quick response. Unfortunately I created a new bucket and a new user with permissions to S3 but cannot recreate the issue. The issue seems to be local to the user.