Please fix my access permissions ASAP—nothing is working for me!!!

My storage is being blocked by “AccessDenied”; all keys have been regenerated, but it still isn't working

I'm losing customers every hour because my buckets aren't working

AccessDenied error on ListObjectsV2 operation - S3 buckets not accessible in production

Hi Railway Support,

I'm experiencing AccessDenied errors when calling the ListObjectsV2 operation on S3, and my objects are not appearing on the website. This is blocking production.

Affected buckets:

• s3-ccxvfyz39j8nmegmsujon0 (ID: 1636b5a0-2511-4683-a496-1881ff477f5b)
• coordinated-organizer-q4rega
• practical-stand-rz8bvl-tu
• s3-jfyxzwdkpdjy7yzctman11

Bucket status:

• All buckets are visible on the canvas
• One bucket contains 923.7 MB of data
• All access keys and credentials are correctly configured and match the bucket settings

Affected services:

• proxy (S3 proxy service) - returns 404 errors when trying to fetch files
• directus (CMS) - configured with S3 storage backend
• admin, site, media-service - also connected to S3

Steps already taken:

• Regenerated all access keys — issue persists
• Verified all environment variables match bucket credentials
• Confirmed reference variables are correctly set up

Project details:

• Project ID: 91e6b3e0-02d6-4b3d-8f70-0610e837469a
• Environment: production (83acc240-4506-42f1-8cc3-35866ac35612)

Could you please investigate the S3 permissions and restore access to these buckets? This is critical for production.

Thank you

Railway Support, are you deliberately ignoring my issue? I can’t restore access to the bucket no matter what I try. This is an issue with your infrastructure—you’ve blocked my access to the bucket, so I can’t download the files or back them up to Cloudflare R2. Please do something about this; four of my client applications have been down for a day now.

I just created a new test bucket and I'm having the same problem—I don't have access.

• Try to redeploy all services. It'll fix the issue.

Same issue was with https://station.railway.com/questions/getting-invalid-login-for-minio-servic-34f1961b

That didn't work, and the bucket is set up with the native Railway service, not Minio. It can't be restarted; the only option is to regenerate the keys—but that doesn't help either.

There is no access to the bucket—not via the Railway CLI, the command line, or SSH. The service does not respond at all to requests and cannot be accessed.

I created a new project and a new bucket, but I can't access it either; for some reason, Railway has blocked all access to any buckets at the infrastructure level.

Everything is working now. I didn't do anything, but it's working. Question closed