a month ago
Hello Railway team,
I’m unable to obtain credentials for newly created Storage Buckets in an isolated staging environment.
Environment:
- Plan: Hobby
- Region: ams (EU West, Amsterdam)
- Railway CLI: 5.26.1
- Bucket is empty and contains no production or personal data
Dashboard behavior:
The bucket storage resource is created, but the deployment displays:
“We couldn't create bucket credentials due to an unexpected error.”
I reproduced this with multiple new empty buckets.
CLI reproduction:
railway login
railway link
railway bucket create --region ams
railway bucket list --json
railway bucket info --bucket --json
railway bucket credentials --bucket --json
The bucket creation succeeds. Both bucket list and bucket info confirm that the bucket exists in ams, with zero objects and 0 B of storage.
However, requesting credentials consistently returns:
BucketInstanceCredential not found
Expected behavior:
The bucket should receive S3-compatible credentials after creation, visible in the dashboard and available through railway bucket credentials.
Actual behavior:
The bucket is provisioned and listed, but no BucketInstanceCredential exists, so it cannot be connected to an application or tested through the S3 API.
Could a Railway team member investigate this? I can provide the project, environment and bucket IDs through a private or secure channel if required.
Thank you.
21 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
+1, is this being investigated?
a month ago
+1, Same Issue
a month ago
same issue +1
a month ago
same issue? are buckets services down?
a month ago
Same issue here
a month ago
Incident raised, you can follow here: https://status.railway.com/incident/6K0GZ5NQ
Status changed to Solved Railway • about 1 month ago
a month ago
Hi Railway team,
The original credential-generation issue appears to be resolved, but the generated credentials still cannot access the bucket.
Current setup:
Environment: staging
Region: ams
Railway CLI: 5.26.1
S3 client: AWS SDK v3
Endpoint: https://t3.storageapi.dev
Region configuration: auto
URL style reported by Railway: virtual-host
Troubleshooting performed:
- Created a new empty bucket from the Railway CLI.
- Retrieved its newly generated credentials.
- Tested both PutObject and ListObjectsV2.
- Tested virtual-hosted and path-style URLs.
- Explicitly selected the staging environment.
- Reset the credentials and retried.
- Deleted the bucket completely.
- Confirmed the environment had no buckets.
- Created another new bucket entirely through the CLI.
- Waited for permission propagation and retried.
Every attempt returns:
- HTTP 403
- Code: AccessDenied
- Message: Access Denied
The newly created bucket remains empty (0 objects, 0 B).
Recent request IDs:
1784200016302628884
1784200063504493181
No credentials or sensitive project identifiers are included here.
Could you please check whether the generated credentials are being attached to the correct bucket policy or storage instance?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hello. I'm blocked.
dev
Should be fixed now
a month ago
Could you please check my last reply?
dev
Incident raised, you can follow here: https://status.railway.com/incident/6K0GZ5NQ
a month ago
https://station.railway.com/questions/after-upgrading-from-free-to-hobby-proje-3ede6443
Same issue with me, can you please check, both my buckets are not working with access denied error and is not fixing with a simple cred regen. I tried deleting and readding buckets as well. This is a major internal issue i think.
a month ago
Hey, sorry for the wait, and thanks for the thorough troubleshooting writeup. You were right that this was on our side.
Two separate things happened here:
- The original credential-generation failure was the July 16 incident you already saw, which was fixed that morning.
- The 403 AccessDenied that persisted afterwards was different: the storage organization backing your workspace's buckets was left in a suspended state with our storage provider after your plan change on July 16. That's why every credential, new bucket, and URL style you tried still returned Access Denied.
We've reactivated it, and I've verified from our side that both ListObjectsV2 and PutObject now succeed against your staging bucket with your current credentials. No regeneration needed.
Please give it a try and let us know if anything still fails.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Resolved, thank you!
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved Railway • about 1 month ago