Object Storage bucket still returning 403 AccessDenied after increasing usage limit
reishapira
HOBBYOP

17 days ago

My object storage bucket is still returning 403 AccessDenied after my services were stopped due to hitting my usage limit.

I've since increased the limit and redeployed my web service, but the bucket remains inaccessible.

I've confirmed the S3 credentials are resolving correctly (non-empty, matching the bucket service), and tested access directly using aws4fetch with the injected env vars — still getting 403.

Everything worked fine before the billing pause. It seems the bucket suspension on the Tigris side wasn't lifted when I updated my usage limit.

Anybody know how to cause the S3 Bucket to start working again? Thanks!

Awaiting User Response

1 Replies

sam-a
EMPLOYEE

16 days ago

We've identified that your bucket suspension wasn't automatically lifted on our storage backend when you increased your usage limit. We're investigating this issue and will manually restore access to your bucket. This should be resolved shortly.


Status changed to Awaiting User Response Railway 16 days ago


Loading...