server
server copied to clipboard
2FA not working with latest docker image
Since updating to the latest Docker image (a9cc00a4783c12e71eb181a3ccf3218b418750d9 or 5446f3cae4b857af3abd51c4b860d7e7c2c857b6) I cannot setup 2FA for my account. I get this message, each time I try to set it up: "Incorrect authentication code, please try again." Any thoughts on why this is happening? My 2FA app works just fine with every other application/website I use it with.
I'm having this same problem, except I'm also running the webapp and can see it's 500ing from my console.
...or at least I could. I checked today, the webapp and the Windows client show disparate information now. The webclient claims I need a paid sub plan (I have both the database tweak plan and an offline sub, so don't know why it's saying that), and the Windows client errors out like OP's post suggests.
My clock is accurate, both clocks get their time from the same sane time source, yet at one point I saw it 500ing in the webapp. I'm going to see if I can reproduce it, but since I haven't touched it in a little while I'm not sure what the deal is between both not showing the same thing.
Regardless, I can't set up 2FA either. It's something under the hood. I can get logs if needed, but I've looked through them to no avail. Nothing remotely in the guise of an error.
I just did a docker-compose pull
tonight to update my images, and I still apparently cannot set the OTP. Web client still shows apparently I'm not subscribed, Windows client still just immediately fails.
Did you by any chance set up your server keys in the env vars? Seems like something related to: https://github.com/standardnotes/server/issues/476#issuecomment-1471648548
I'm not able to check right now, but I'll take a look at next available opportunity! 😄
I do believe I have an older .env
. Let me see if I can copypasta the old values I've got into the new template I see here. I have a sneaking suspicion this was in fact the cause of my problem, as there's some values I wasn't aware have to be here now.
EDIT: It now matches, but I still get a 500 when I check in the console, even after a pull to the latest version.
anything in the logs?
Nothing that would indicate something in the negative. I'm going to reroll my instance later today and see if it was something in my db, and report back.
EDIT: I had enough time today and fortunately not a lot of use, so I just rerolled. 2FA enabled finally, so I think I had some keys that were still in the DB not jiving.
@bigjdunham You might have to reroll, but it at least enables now as of the latest Docker image.