Unable to Login

[qusaialhaddad]

Installed by using docker , installation success , but didnt see any credentials during docker installation , I have updated the .env file with user and password as per the instruction , but still cannot login.

[ooovenenoso]

For Docker installs, the initial credentials are usually in the container logs, not necessarily printed directly in your current terminal.

Try:

docker compose logs odysseus | grep -i "temporary password"

The default username is admin unless you configured a different admin user.

If data/auth.json was already created on a previous boot, changing the admin-related .env values afterwards will not recreate the existing login. In that case either:

1. stop the container,
2. remove/reset data/auth.json from your Odysseus data directory,
3. start Docker again,

or log in with the existing credentials and change them in Settings.

For Docker, this matches the README note: the temporary password line is in docker compose logs odysseus.

[eduardo98m]

@ooovenenoso I had the same problem as the user above, would this be considered an issue?

-> If a user changes the .env admin credentials and restarts the container shouldn't the new credentials in the .env file be the valid ones? It is not very intuitive to know before hand that you have to delete the data/auth.json file.

I asked a coding agent and a possible fix is changing the function create_default_admin in the setup.py file.

[ooovenenoso]

@eduardo98m I’d treat that as a UX/feature-request issue rather than a simple “the env vars are broken” bug.

Right now the behavior is one-time bootstrap: ODYSSEUS_ADMIN_USER / ODYSSEUS_ADMIN_PASSWORD are used when the first admin record is created. After data/auth.json exists, that file is the source of truth, so restarting with different .env values should not silently overwrite an existing admin account/password.

The reason I’d be careful with automatically syncing .env into auth.json is that it could unexpectedly reset credentials later, or overwrite a password the admin changed in Settings. A safer issue/proposal might be one of:

• document this more clearly in the Docker setup/login section,
• log a clear warning when auth already exists and bootstrap env vars are ignored,
• add an explicit reset/bootstrap command or setting,
• only support env-driven reset behind an explicit opt-in flag.

So yes, worth opening as a UX improvement if there isn’t already an issue for it — but I wouldn’t make normal restarts automatically rewrite data/auth.json.

[ChiefHairyNPZ]

dont know if u fixed this but saying it simply

temp user and password: "admin" if not changed b4, for the password on the docker app go to logs and type in password

for me it was a bunch or random letters and numbers.
hopefully this small bit of insite helps

[bitboody]

This is a little bit of a hack more than a solution, but if you remove data/auth.json and re-run python setup.py, you should receive a new password.

Note: you only get the password the first time you run the setup script.