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)"} -
@Maxim Looks like same as https://github.com/outline/outline/issues/7638
-
Did you happen to set up oauth in outline previously? There is a workaround in https://github.com/outline/outline/issues/7638#issuecomment-2369775288 . I haven't managed to reproduce this issue so I can't say if it works or not.
-
-
-
@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.