Sincerely i dont think this can be solved by public opinions. Someone from Railway team need to force reset my credentials/access to match the new Hobby plan

Have you try regenerate the credentials by yourself? you can try reset it by opening the bucket service and go to the credentials tab and click the Regenerate Credentials button

Tried regenerate before as well, didnt work, tried it now, still doesnt work and now with a different error.

As i said i think this has to do something internally

The error changed back to initial error after a while. I think its a permission issue which we dont have access to change/fix

check the S3 endpoint and region configuration.

It may be possible the project was moved to a different cluster during the upgrade, changing those details and causing the mismatch with the old credentials.

Redeploy after changing region or s3 endpoint configurations

Can you help me with how to do this? I cant find any option to check endpoint, region is set to South East Asia / Singapore on all services in that project

Endpoint URL is https://t3.storageapi.dev and i cant change it

This is seriously frustrating and hurting the development of my project as im unable to test anything without storage/bucket access. Can someone from the staff help me out here to clear this issue. Both my project buckets show the same exact error and doesnt get fixed by just regenerating the credentials or deleting the whole bucket and creating a new one. Nothing works on my end. I saw couple more thread like this, believe they weren't solved either. Do you want us to upgrade to Pro just so you can reply? Is that the plan here?

Same error on my side, I have this open issue: https://station.railway.com/questions/bucket-credentials-are-not-generated-aft-d102636c

Exactly this has to be a internal technical issue that is not resolvable by public advices, this has to be an internal technical issue. And since many people are facing the same issue, they should atleast put an article out on how to fix this (if its ever fixable from our end). Why waste so much time (2 days now without an answer) going around something that is not fixable from outside involvement?

NEED RAILWAY BACKEND/BUCKET TECHNICAL HELP TO RESET/RESTORE THE PERMISSIONS FROM BACKEND PLEASE

2+ days without a proper response from tech support for an issue we can fix from our end and my projects are on hold in development

navigate to Account Settings > Billing to ensure there are no pending verification banners or failed charge notices.

Hey, sorry for the wait on this one. You were right that this was internal and not fixable from your side.

When your workspace changed plans, the storage organization that backs your buckets was left in a suspended state on our storage provider's side, which is why every request returned Access Denied no matter what you tried. We've reactivated it, and I've verified your bucket is accessible again (your existing credentials work, no regeneration needed).

Please give it a try and let us know if anything still fails. Apologies again for the disruption to your development.

Thank you so much. It works now. Please create a way to contact you guys in case of such technical issue happen for all users, this can be really helpful for everyone

Glad it's working again, and sorry for the delay. I want to take this opportunity to mention that this support form is the way to reach us. However, the response time for Hobby users is up to 7 days.