Troubleshooting
“No Diteko server answered at …”
Section titled ““No Diteko server answered at …””The Python package could not reach a server. Check the server is up (docker compose ps), and
that DITEKO_URL points at it. The package defaults to http://localhost:8080.
“… is not a Diteko server”
Section titled ““… is not a Diteko server””Something answered at that address, but not Diteko: another service on the same port, or a proxy
page. Check the port in DITEKO_URL, and DITEKO_PORT in the server’s .env.
401 on every call
Section titled “401 on every call”The key is missing, mistyped or revoked. Keys start with dk_. The console forgets a key only when
the server rejects it, so a server outage does not log you out.
403 on a call
Section titled “403 on a call”The key is valid but its scope does not allow that call. See keys and scopes.
“Import from Connect” says Connect is not configured
Section titled ““Import from Connect” says Connect is not configured”The server has no Connect settings, or they were not loaded. Set the DITEKO_CONNECT_* values in
.env and run docker compose up -d again. See self-hosting.
Errors after an upgrade (InvalidClassException)
Section titled “Errors after an upgrade (InvalidClassException)”Redis holds cached data in the previous version’s format. Clear it:
docker compose exec redis redis-cli FLUSHALL. Nothing is lost; the cache refills itself.
A test failed on Connect but looks right
Section titled “A test failed on Connect but looks right”Open it in Results and look at the step it stopped at. If it passed on a re-run, Connect most likely missed a prompt the first time. If a precondition says it could not be staged (a value a test cannot set), Connect took whichever branch the real value led to.
A run says “Interrupted”
Section titled “A run says “Interrupted””The server restarted while it was in progress. Start the run again.