a month ago
Creating a new bucket succeeds, but credential provisioning always fails.
Project: total_module / environment: production / region: sjc
Plan: Hobby
New bucket: businesscard_qr_bucket (ID dd6e4dfe-d23f-459e-82e3-16b4bfacade9)
- railway bucket credentials -> "BucketInstanceCredential not found"
- railway bucket credentials --reset -> "We couldn't create bucket credentials due to an unexpected error."
- Dashboard Credentials tab shows the same "unexpected error"
Existing bucket: doll_gacha_bucket (ID 17f62c9a-2222-428d-8338-11cc155f28f0), same project/region
- credentials return normally
What I already ruled out:
- Not region (both sjc)
- Not the name (recreated via CLI with a clean name)
- Not the dashboard (CLI v5.26.1 fails identically)
- Not a platform incident (status page shows Buckets 100% operational)
- Docs state no limit on number of buckets per project
The bucket itself is created (has ID/region), only the credential record is never provisioned.
Is there an account-level issue, or is this a bug in credential provisioning?
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hey! This was a platform-wide bug in bucket credential provisioning on July 16 (status page: https://status.railway.com/incident/6K0GZ5NQ). It only affected credential creation, which is why your existing bucket kept working while the new one failed. It was fixed the same day.
Please run railway bucket credentials --reset for businesscard_qr_bucket again. It should now provision correctly. If it still fails, reply here and we'll take a closer look.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 28 days ago