-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
I just updated from an older version (v2.something to v3.10.2), but after the upgrade I have been unable to log in via the URL.
As a test, I've wiped the entire container and started from scratch, and I was unable to log in even with the default credentials shown on the page.
I then followed through and attempted to log in using the IP and port instead of the URL, and noticed I was able to log in without an issue.
Only the Mealie and PostgreSQL versions have changed (initially only Mealie, PostgreSQL was updated in case that was the problem when I wiped and started fresh).
Any assistance on how to get this working again, or pointing me to whatever change/s may have caused this, would be appreciated.
Logs for the attempts below:
mealie | INFO 2026-02-05T22:08:02 - [10.0.0.29:0] 200 OK "POST /api/auth/token HTTP/1.1"
mealie | INFO 2026-02-05T22:08:02 - [10.0.0.29:0] 401 Unauthorized "GET /api/users/self HTTP/1.1"
mealie | INFO 2026-02-05T22:08:11 - [10.0.0.29:0] 200 OK "POST /api/auth/token HTTP/1.1"
mealie | INFO 2026-02-05T22:08:11 - [10.0.0.29:0] 401 Unauthorized "GET /api/users/self HTTP/1.1"
mealie | INFO 2026-02-05T22:08:24 - [10.0.0.29:0] 200 OK "POST /api/auth/token HTTP/1.1"
mealie | INFO 2026-02-05T22:08:24 - [10.0.0.29:0] 401 Unauthorized "GET /api/users/self HTTP/1.1"
mealie | INFO 2026-02-05T22:08:28 - [127.0.0.1:59114] 200 OK "GET /api/app/about HTTP/1.1"
mealie | ERROR 2026-02-05T22:08:28 - Incorrect username or password from 10.0.0.29
mealie | ERROR 2026-02-05T22:08:28 - Incorrect username or password from 10.0.0.29
mealie | INFO 2026-02-05T22:08:28 - [10.0.0.29:0] 401 Unauthorized "POST /api/auth/token HTTP/1.1"
The last one is me testing whether an intentionally incorrect password gave a different response