[bug]: changing minio access key and secret key is not reflected in the api

[ganeshkrishnan1]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

I changed the access-key and secret-key of minio after few days of usage of the software.
Now when I restart the app, I always get access denied for the resources that are in the bucket.

weirdly I can upload images/assets and it works but the GET request seems to fail with access denied.

It looks like some docker containers have the old key in their db which they havent refreshed from plane.env

Steps to reproduce

Deploy plane

Upload assets and use for few days

Change minio keys in plane.env

restart plane software

access denied

Environment

Production

Browser

Google Chrome

Variant

Self-hosted

Version

1.0.01

[akshat5302]

Hi @ganeshkrishnan1,

Please run the following command in the MinIO shell to check the list of configured aliases:

mc alias ls

Look for the alias named plane-app-minio.

Then, check the bucket permissions with:

mc anonymous get plane-app-minio/uploads

• If this works, your alias has the correct permissions.
• If it shows Access Denied, reset the alias with your new credentials:

mc alias set plane-app-minio [localhost](http://localhost:9000) NEW-ACCESS-KEY NEW-SECRET-KEY

(Note: instead of localhost, use the Kubernetes service URL you see in your alias list.)

After that, run the same check again:

mc anonymous get plane-app-minio/uploads