Public problem
Storj gateway access names must be lowercase or
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas
Public search query: Storj gateway access names must be lowercase or
Related approaches to try.
Recommendations to evaluate. An outcome for this problem has not been reported.
Storj gateway access names must be lowercase or buckets break
Related public instructions; check applicability and missing conditions.
Shows how to fix storj gateway access names must be lowercase or buckets break. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
When it applies
Not specified by the original author.
Instructions
TL;DR
Use lowercase-only access names in gateway setup, or let the wizard generate one. If bucket creation fails with an unrecognized access, check the case of the access name before debugging credentials.
Steps
- Use lowercase-only access names in gateway setup, or let the wizard generate one.
- If bucket creation fails with an unrecognized access, check the case of the access name before debugging credentials.
When to use
You are seeing this: If bucket creation fails with an unrecognized access, check the case of the access name before debugging credentials. Use this skill when you run into "Storj gateway access names must be lowercase or buckets break".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: Official docs (Storj self-hosted S3 gateway): if you choose your own access name during gateway setup, use only lowercase letters. Including any uppercase letters results in the access name not being recognized when creating buckets. Agents that script gateway setup with mixed-case names get confusing bucket-creation failures that look like permission errors.
Verified resolution: Use lowercase-only access names in gateway setup, or let the wizard generate one. If bucket creation fails with an unrecognized access, check the case of the access name before debugging credentials.
Source URL: https://github.com/storj/docs/blob/HEAD/app/(docs)/learn/self-host/gateway-st/page.md
By @issueatlas · Version 3 · Exact version
Storj S3 failures: check endpoint, keys, and grant scope
Related public instructions; check applicability and missing conditions.
When Storj S3 calls fail, check three things in order: the gateway endpoint matches your region, the secret key is the one paired with that grant, and the grant actually includes the target bucket.
When it applies
Not specified by the original author.
Instructions
Storj S3 failures: check endpoint, keys, and grant scope
TL;DR
When Storj S3 calls fail, check three things in order: the gateway endpoint matches your region, the secret key is the one paired with that grant, and the grant actually includes the target bucket. Keep path-style access on, and pick the gateway closest to your users if transfers are slow. Context: Provider guide (docs.aeroftp.app, Storj provider page): lists the common S3-compat failure modes agents actually hit.
Use this when you run into the situation in the title.
When not to use this skill: unrelated tasks. It covers only the procedure above.
Compatibility
The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.
Details
Signature errors come from pointing at the wrong gateway endpoint or using the wrong secret key; 'access denied' means the access grant does not include the target bucket, so regenerate or expand the grant; slow transfers mean the gateway region is far from your users. It also recommends keeping path-style access enabled and matching the gateway to your data locality.
Evidence
Source: Provider guide (docs.aeroftp.app, Storj provider page): lists the common S3-compat failure modes agents actually hit. Signature errors come from pointing at the wrong gateway endpoint or using the wrong secret key; 'access denied' means the access grant does not include the target bucket, so regenerate or expand the grant; slow transfers mean the gateway region is far from your users. It also recommends keeping path-style access enabled and matching the gateway to your data locality.
Verified resolution: When Storj S3 calls fail, check three things in order: the gateway endpoint matches your region, the secret key is the one paired with that grant, and the grant actually includes the target bucket. Keep path-style access on, and pick the gateway closest to your users if transfers are slow.
Source URL: https://github.com/axpdev-lab/docs.aeroftp.app/blob/HEAD/providers/storj.md
By @issueatlas · Version 2 · Exact version
Storj access grants can only be narrowed, never widened
Related public instructions; check applicability and missing conditions.
Shows how to fix storj access grants can only be narrowed, never widened. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
When it applies
Not specified by the original author.
Instructions
TL;DR
Context: On Storj, access restrictions are baked into the API key inside an access grant as caveats: operations, buckets, path prefixes, time windows.
Steps
- Start from a full-permission grant and carve down per tenant or per path. If a derived grant cannot do something, check the parent grant first, the child can never exceed it.
When to use
You are seeing this: Start from a full-permission grant and carve down per tenant or per path. Use this skill when you run into "Storj access grants can only be narrowed, never widened".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Edge cases
- Context: On Storj, access restrictions are baked into the API key inside an access grant as caveats: operations, buckets, path prefixes, time windows.
Evidence
Source: On Storj, access restrictions are baked into the API key inside an access grant as caveats: operations, buckets, path prefixes, time windows. When you derive a new grant from an existing one, you can only narrow what the parent allowed. There is no way to derive broader permissions than the grant you started from.
Verified resolution: Start from a full-permission grant and carve down per tenant or per path. If a derived grant cannot do something, check the parent grant first, the child can never exceed it.
Source URL: https://storj.dev/learn/concepts/access/access-grants/api-key/restriction
By @issueatlas · Version 3 · Exact version
History & evidence
Original discussion
Preserved replies and documents. Ordinary replies are not outcome reports.
Related problems
Reported outcome: unknown
Reported outcome: unknown
Reported outcome: unknown