New Users can't Login

[Morphyum]

Hi,
we currently run into a Problem with a selfdeployed openCore 1.5.11.117:
When we create new users they are unable to login its not an isolated problem since one of our customers also faces the same Problem.
@lars.mielke can provide logs from the server but this seems to be the main problem:

9:24:24.121  [LoginProvider        ][CreateLocalStrategy]   Passwordhash cannot be empty
9:24:24.121  [LoginProvider        ][Localauthenticate]     Passwordhash cannot be empty
9:24:24.279  [Message              ][Process]               Not signed in, and missing jwt
query failed with: Not signed in, and missing jwt
Error: Not signed in, and missing jwt
    at protowrap.IsPendingReply (file:///app/dist/public/server/chunks/auth.svelte-BLPHmr0H.js:12225:41)
    at parser.ondata (file:///app/dist/public/server/chunks/auth.svelte-BLPHmr0H.js:12029:31)
    at messageParser.write (file:///app/dist/public/server/chunks/auth.svelte-BLPHmr0H.js:11884:18)
    at ws.onmessage (file:///app/dist/public/server/chunks/auth.svelte-BLPHmr0H.js:12019:20)
    at callListener (file:///app/dist/public/server/chunks/auth.svelte-BLPHmr0H.js:15878:15)
    at WebSocket.onMessage (file:///app/dist/public/server/chunks/auth.svelte-BLPHmr0H.js:15797:10)
    at WebSocket.emit (node:events:524:28)
    at Receiver.receiverOnMessage (file:///app/dist/public/server/chunks/auth.svelte-BLPHmr0H.js:17318:21)
    at Receiver.emit (node:events:524:28)
    at Receiver.dataMessage (file:///app/dist/public/server/chunks/auth.svelte-BLPHmr0H.js:14831:15) {
  serverstack: '',
  code: 0
}
core-web version 0.1.2.14 git commit 83456ae opencore version 1.5.11.117

All we do is:

1. Go to users
2. Create a new user
3. Logout
4. Try login with the new user

Greetings Marvin

[Allan_Zimmermann]

Damn it, you are right, will fix asap

[Allan_Zimmermann]

This been fixed now … if you are using “latest” tag, do a docker compose pull ( for instance normal-pull ) if you are using a fixed version change it to “1.5.11.121”

[Allan_Zimmermann]

i messed up something while pushing the “latest” tag … but it’s working now