[Bug]: signin does not work

[ptulpen]

Summary

After installing defguard 2 with docker compose I setup everything normal, but when I log in again, mylogin does not work again
This happned twice now. (After the first time, I reinstalled)

Steps to reproduce

• Install with the setup wizard.
• Close browser
• At login in again, login fails

Expected behavior

Login working

Actual behavior

The container log tells:
Authenticated user XXX

when trying with a wrong password, I get correctly:
"Logging failed login attempt for username"

Defguard version

2.0

Environment details

ubuntu 24.04

Deployment / install method

Docker / Docker Compose

Relevant logs / output

2026-05-05T14:54:54.663530Z  INFO http_request{method=GET path=https://10.3.196.34:8000/assets/icons/favicon.ico}: tower_http::trace::on_response: message=finished processing request latency=0 ms status=200
2026-05-05T14:54:54.667029Z  INFO http_request{method=GET path=https://10.3.196.34:8000/assets/icons/favicon.ico}: tower_http::trace::on_response: message=finished processing request latency=0 ms status=200
2026-05-05T14:54:59.327733Z  WARN http_request{method=POST path=https://10.3.196.34:8000/api/v1/auth}: defguard_core::handlers::auth: message=Failed to authenticate user mwigger: invalid password
2026-05-05T14:54:59.327804Z  INFO http_request{method=POST path=https://10.3.196.34:8000/api/v1/auth}: defguard_core::auth::failed_login: message=Logging failed login attempt for username mwigger
2026-05-05T14:54:59.327861Z  INFO http_request{method=POST path=https://10.3.196.34:8000/api/v1/auth}: tower_http::trace::on_response: message=finished processing request latency=14 ms status=401
2026-05-05T14:57:46.031860Z  INFO proxy_bidi:http_request{method=POST path=https://10.3.196.34:8000/api/v1/auth}: defguard_core::handlers::auth: message=Authenticated user mwigger [2.0.0][PX:2.0.0+f19803c]
2026-05-05T14:57:46.038586Z  WARN defguard_mail::mail: message=SMTP not configured, email sending skipped
2026-05-05T14:57:46.038795Z  INFO proxy_bidi:http_request{method=POST path=https://10.3.196.34:8000/api/v1/auth}: tower_http::trace::on_response: message=finished processing request latency=25 ms status=200 [2.0.0][PX:2.0.0+f19803c]
2026-05-05T14:57:46.060255Z  INFO http_request{method=GET path=https://10.3.196.34:8000/api/v1/session-info}: tower_http::trace::on_response: message=finished processing request latency=1 ms status=200
2026-05-05T14:57:46.264978Z  INFO http_request{method=GET path=https://10.3.196.34:8000/api/v1/session-info}: tower_http::trace::on_response: message=finished processing request latency=0 ms status=200
2026-05-05T14:57:46.270258Z  INFO http_request{method=GET path=https://10.3.196.34:8000/assets/icons/favicon.ico}: tower_http::trace::on_response: message=finished processing request latency=0 ms status=200
2026-05-05T14:57:46.276413Z  INFO http_request{method=GET path=https://10.3.196.34:8000/assets/icons/favicon.ico}: tower_http::trace::on_response: message=finished processing request latency=0 ms status=200

Relevant configuration (redacted)

[jakub-tldr]

Hello @ptulpen,

I tried to reproduce this on a fresh docker compose setup and couldn't get it to fail. Could you double-check that you're using the exact same credentials you set during the initial setup wizard?

If you're certain the credentials are correct and still can't log in, please let us know.

[jakub-tldr]

Closing this issue due to inactivity.

If the problem is still occurring, feel free to reopen the issue or create a new one with additional details, and we’ll be happy to help.

[ptulpen]

Hello and sorry for the delayed answer. Unfortunately this happens again

• Fresh install
• created a new user
• just logging out and trying to login again.
• does not work with both users

Any ideas how to further troubleshoot?