Setup token not accepted
What went wrong
Section titled “What went wrong”On /setup you see one of:
- “That token isn’t right. Check the container logs for setup_token=…”
- “Too many attempts. Wait 15 minutes and try again.”
- “Too many wrong tokens. Restart the container to get a new one.”
- “Your setup session expired. Reload the page and enter the token again.”
Why it happens
Section titled “Why it happens”- Wrong token: a new token is generated each time the container starts, so an old one from earlier logs no longer works. Copying with extra spaces or a missing character also fails.
- Too many attempts: one address can try 5 tokens every 15 minutes.
- Too many wrong tokens: after 20 wrong tokens from anywhere, the token is cancelled to stop guessing.
- Session expired: after the token is accepted you have 30 minutes to finish the form.
How to fix it
Section titled “How to fix it”-
Get the token from the current container’s logs:
Terminal window docker compose logs app | grep setup_token= | tail -1 -
For “too many wrong tokens”, restart to get a new one:
docker compose restart app, then repeat step 1. -
For an expired session, reload
/setupand enter the token again.
To avoid tokens altogether, set ADMIN_EMAIL and ADMIN_PASSWORD and restart, or choose your own with SETUP_TOKEN.
See also
Section titled “See also”- First-run setup: both ways to create the first admin