-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated passwords are refused #138
Comments
I get the same behaviour as well today. A few days ago I also noticed that it took a couple of trials until my OTP was accepted by my service. Today they didn't work at all |
is your system set up with NTP or similar? my guess is your system clock has drifted over 30seconds or more, so you're getting different codes. i recommend chrony as an arch linux user; arch docs that may be helpful to any GNU/Linux users |
Bummer, that was too obvious to miss. You were right @maxthomas! I was about 2 minutes away from real time... |
So simple! Thanks for the chrony tip, the issue can be closed i guess. |
Hi,
Thanks a lot for
pass-otp
it's awesome !I'm trying setting it up but for some reason none of the codes I get are accepted server-side... I think my URIs are correctly set up though, as an example
otpauth://totp/XXXXXXXXXX?secret=****************&issuer=Discord&digits=6&period=30&algorithm=SHA1
But the generated passwords are all different from the ones I have on andOTP (is this normal?) and are refused. Could it be a clock issue? I don't really know how to probe for this, any clue?
The text was updated successfully, but these errors were encountered: