mirror of
https://github.com/fosrl/pangolin.git
synced 2026-11-13 06:14:30 -06:00
TFA is not reliable #213
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/pangolin#213
Reference in New Issue
Block a user
Originally created by @kylepyke on GitHub (Apr 5, 2025).
Two factor authentication does not always work. I enter my credentials, then I'm taken to the TFA screen. I enter the TFA token according to my linked authenticator. The code does not work, with the error "The two-factor code you entered is incorrect", even when it is correct.
@kylepyke commented on GitHub (Apr 5, 2025):
Closing and reopening the authenticator app seems to have fixed this.
@maxwassiljew commented on GitHub (May 23, 2025):
I’m still seeing this exact problem: after entering correct credentials I’m prompted for 2FA, but the valid TOTP code from my authenticator is always rejected with: The two-factor code you entered is incorrect
tested with: Vaultwarden and OTP Auth
@kylepyke What authenticator app do you use?
@kylepyke commented on GitHub (May 23, 2025):
I use DUO and still get this error from time to time. The fix seems to be: 1. Close the auth app; 2. Reload the Pangolin login page; 3. Reopen the auth app.
This does still seem to be a bug…
@maxwassiljew commented on GitHub (May 23, 2025):
Thank you, I will recheck with DUO. Right now I'm trying this solution: #106
@DarrenYOW commented on GitHub (May 23, 2025):
I've been intermittently having the same issue using Aegis. A browser refresh usually "fixed" it. Turns out I had the exact same NTP problem described in #106. UPDATE: Issue has not recurred since applying the NTP fix.
@github-actions[bot] commented on GitHub (Jun 18, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@oschwartz10612 commented on GitHub (Jun 18, 2025):
Yeah everyone having MFA issues please make sure your VPS always has the right time and the NTP is working. That almost always fixes this. If not please open a new issue!