Authentication failed on Package Version 1.6.0
-
When upgrading to Package Version 1.6.0, the User issues an error when logging in via authenticate with the Cloudron: "Authentication failed – we were unable to sign you in at this time. Please try again." When returning to the backup with the v1.5.1 package, the error disappears. What is the reason?

logs:
{"error":"User authentication gushchin already exists for 0050c1c4-c308-4d25-8c12-02c0095e3ada, tried to assign to 2a735ef7-41ed-4be0-9a66-b6d03226b0c8","level":"error","message":"Error during authentication","stack":"Error: User authentication gushchin already exists for 0050c1c4-c308-4d25-8c12-02c0095e3ada, tried to assign to 2a735ef7-41ed-4be0-9a66-b6d03226b0c8\n at userProvisioner (/app/code/build/server/commands/userProvisioner.js:56:13)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async accountProvisioner (/app/code/build/server/commands/accountProvisioner.js:79:12)"} -
N nebulon marked this topic as a question on
-
N nebulon has marked this topic as solved on
-
@Maxim yeah deleting that helped
DELETE FROM user_authentications;
In our family one user got the same problem.
The message in German is:
"""
Authentifizierung fehlgeschlagen - wir konnten dich zu diesem Zeitpunkt nicht anmelden. Bitte versuche es erneut.
"""The App Event log in cloudron did not show any error, only the logs.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login