Troubleshooting¶

Fleet won't start: private key too short¶

Error:

private key must be at least 32 bytes long

Fix:

openssl rand -base64 32

Use that value for FLEET_SERVER_PRIVATE_KEY.

Fleet won't start: missing server private key¶

If FLEET_SERVER_PRIVATE_KEY is empty or missing, Fleet will exit. Generate one and set it via environment variables:

openssl rand -base64 32

Then re-run the container with:

-e "FLEET_SERVER_PRIVATE_KEY=your-generated-key"

MySQL permission errors¶

If you see errors about /data/mysql permissions, verify your PUID/PGID:

id

Then pass those values when you run the container.

If the volume was created with a different user, fix ownership on the host:

sudo chown -R 1000:1000 /path/to/fleet-data

Redis config permission error¶

If Redis cannot read /etc/redis/redis.conf, make sure the container is not running as a non-root user. The container expects to start as root and then drop privileges.

Can't reach Fleet UI¶

Confirm the container is running:
```
docker ps
```
Check logs:
```
docker logs -f fleet
```
Make sure port 1337 is mapped (-p 1337:1337).

If you changed the host port, update the URL accordingly (for example http://localhost:8080).

Slow startup on first run¶

The first boot runs MySQL + Fleet migrations. This can take a minute. Subsequent starts are much faster.