Fix Odysseus invalid credentials

If Odysseus says "invalid credentials", slow down before deleting volumes. The usual causes are using the wrong first-run admin password, missing logs, changed auth environment variables, or a reset that did not touch the persistent database.

1. Check first-run logs

For Docker Compose installs, inspect the Odysseus service logs. The first generated password or setup instruction is often printed during initialization.

docker compose logs odysseus

If you are not sure about the service name, list compose services first:

docker compose ps

2. Confirm you are using the right account

Check whether the username is email-based or admin-based in your current version.
Make sure you copied the password without spaces or hidden line breaks.
Try a private browser window to avoid stale cookies.
Do not assume the GitHub README password from another version applies to your install.

3. Check auth-related environment variables

If you changed auth settings, compare your current .env or compose environment with the official example. A mismatched admin password variable, disabled auth flag, or stale database can produce confusing login behavior.

4. Understand volumes before resetting

Deleting containers is not the same as deleting persistent data. If the database is stored in a volume, recreating the container may keep the old credentials. Back up data before any destructive reset.

docker compose down
docker volume ls

Safe reset order

Save logs.
Back up volumes or appdata.
Confirm the official reset method for your Odysseus version.
Only then reset credentials or recreate persistent state.

Security note: If Odysseus was exposed outside your LAN while credentials were unknown, rotate secrets and review reverse proxy access logs after recovery.