## 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

1. Use lowercase-only access names in gateway setup, or let the wizard generate one.

2. 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.