MinIO Custom Region Problem

Question

I've been using MinIO for some time and I made the mistake of setting a custom "region" name via the MinIO Console Dashboard. MinIO typically doesn't have any region value when first deployed on Railway, after I set a region value (us-west-rack1), I've lost my access. The correct login credentials are not working anymore and when I check the logs i see:
"ErrorWithContext:The authorization header is malformed; the region is wrong; expecting 'us-east-1'."

I've tried redeploying it with "MINIO_REGION" and "MINIO_REGION_NAME" env variables with the value of 'us-west-rack1' but still can't have access. (tried us-east-1 as well as suggested on the error msg but that also didn't work)..

I wonder 2 things:
- If someone had a similar problem and knows how to fix
- If I create a new MinIO service from the Railway template and disconnect the old volume and attach it to the new MinIO service, would that magically work? Could I recover my data considering I create the buckets manually again with the same names)?

Any help is appreciated here!

mertzamir · Accepted Answer

If anyone else has a similar issue, this is fixed, check below for some info:

I resolved this problem by creating another MinIO and attaching my old volume to the new service! So the answer to my 2nd question above turns out to be yes, I could recover all my data.

I wouldn't suggest manually changing the "region" of your MinIO service, because no matter what I tried I couldn't gain access back. Things I've tried but yielded no results:
- Using MINIO_REGION and MINIO_REGION_NAME env vars to override the value and redeploy (didn't help)
- Using the mc cli tool (you have to ssh into your minio bucket for this) to override the region over terminal (couldn't do it, kept giving access denied as expected..)

Hope it's helpful for any future similar problems!