can't enable 2FA, now can't log in! --- Redis issues
-
Redis didn't crash (yet) but it's getting there. Now it's 95% full and I haven't been using the app!
-
Redis didn't crash (yet) but it's getting there. Now it's 95% full and I haven't been using the app!
@humptydumpty What happens when you restart Redis?
-
If I restart Redis, it goes down a bit, but rises after a while.
-
It looks like the Leantime app using redis is not using it well, not freeing memory. Needs to be more lean with Redis
@robi can this be fixed in the packaging or should I report this upstream?
-
@robi can this be fixed in the packaging or should I report this upstream?
@humptydumpty upstream.
-
@humptydumpty upstream.
@robi Thanks. I reported this upstream here: https://github.com/Leantime/leantime/issues/1780
-
It looks like this will take a while to get fixed upstream. Is it possible to disable Redis for now?
-
It looks like this will take a while to get fixed upstream. Is it possible to disable Redis for now?
-
G girish has marked this topic as solved on
-
@girish Thanks for the update!
-
I created a new user. I clicked on the invite email that Leantime sent and set a password for the new account. Then, I activated 2FA. I logged out and tried to log back in and ran into the same login error. However, resetting the password seems to fix the issue permanently. Something is corrupting the passwords on newly create accounts including the admin account that the package creates on first install.
To make this short, there are two issues that need looking into:
- Redis OOM - I have it set to 1GB, and it's 80% full on idle.
- Password Corruption - for all accounts and can be fixed by resetting the password and issue is gone permanently.
@humptydumpty Did you manage to get Two Factor Authentication (2FA) working?
After initial creation of an account, I tried to set up 2FA, but it wouldn't let me.
-
Yes, itโs working fine. Youโre probably running into the issue where the password gets corrupted on first login. Log out, reset the password using the forgot pass button and try 2fa again. Iirc, this is fixed in the next upstream update.