Common problems when installing and running Anasaki Studio, with causes and fixes — from a system that won't start and a forgotten admin address to email that never arrives
docker compose ps # status of both containers (mysql, studio)
docker compose logs -f studio # Anasaki Studio's log
docker compose logs mysql # the database's log
docker compose up says set JWT_SECRET / set MYSQL_PASSWORD / set CODE_DB_PASSWORD
Required values are missing from .env (or .env is not next to docker-compose.yml) — see .env variables
studio keeps waiting / cannot reach the database
MySQL has not finished starting (studio waits for its health check) — see docker compose logs mysql. Special characters in passwords can break the connection string; use letters and digits only
Changed MYSQL_PASSWORD and the database refuses
The password is read only when the database is first created. Use the old value, or change the password in MySQL yourself to match
http://…:8090 does not open
The port is taken — change PORT in .env; or the server's firewall blocks it
A second site on the same machine replaced the first
Give each folder a different COMPOSE_PROJECT_NAME and PORT
Forgot the changed admin address (/admin is a 404)
Put ADMIN_PATH=admin in .env and run docker compose up -d (Security)
Everyone was signed out at once
JWT_SECRET changed — expected; sign in again
Sign-in refused with "too many failed attempts"
10 wrong passwords in 15 minutes from one IP (answers slow down from the 4th). Wait 15 minutes or sign in from another network — if it happens to everyone at once, see "Behind a reverse proxy" below
Must sign in again after upgrading to 2.3.0
Expected: the admin keeps its session in an HttpOnly cookie instead of localStorage (page scripts cannot read it). Sign in once — scripts and the CLI keep using Authorization: Bearer
Forgot the password and email is not set up
Ask another administrator to set a new password under Users
Signing in says the account is suspended
An administrator suspended it — they press Activate on the Users page. Every attempt is in the Activity log
The server has no internet access — you can still install a .zip on the Upload .zip tab
"The package signature is not valid" / "sent without a signature"
The package was changed on the way or does not come from the store the site trusts (CMS 2.4.0). Try again; with your own store check STORE_URL / STORE_PUBLIC_KEY (Installing plugins)
A plugin switched itself off after an update
The new version asks for more permissions — press Approve and activate (Plugin permissions)
Activation fails / needs another plugin first
Install and activate the required plugins first (the dialog offers Install all)
Turn on Safe mode on the Site Code page; if the admin itself is unreachable, add SITE_CODE_DISABLED: "true" under environment: of the studio service in docker-compose.yml and run docker compose up -d
The database page says "fallback mode" and the SQL console is unavailable