mirror of
https://github.com/pocket-id/pocket-id.git
synced 2026-02-05 00:39:38 +03:00
🐛 Bug Report: Not able to use email based login (Says One time access code must be used on the device it was generated for. Please try again.) #581
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @murtaza-nasir on GitHub (Jan 3, 2026).
Reproduction steps
I just updated to v2. Email based login was working before the update.
Reproduction:
Expected behavior
It should sign-in to pocket-id or the App using this for SSO
Actual Behavior
Pocket ID Version
v2.0.1
Database
SQLite
OS and Environment
docker managed via portainer on Ubuntu 24.04.3 LTS
Log Output
_pid-pocket-id-1_logs.txt
@stonith404 commented on GitHub (Jan 3, 2026):
Are you opening the link from the email in the same browser as you have requested the login code?
@daniel100097 commented on GitHub (Jan 3, 2026):
Same issue here, same browser tab.
An generated code via admin works but only if the code does not get sent via email. Maybe my email provider is trying to fetch it ?
@murtaza-nasir commented on GitHub (Jan 3, 2026):
Yes, it is the same computer, same browser. Ideally, I would like this to work as long as I have the code (like it works with services like Claude etc).
@murtaza-nasir commented on GitHub (Jan 3, 2026):
This is what I see in the console. I think this is the same error as #1188.
@murtaza-nasir commented on GitHub (Jan 3, 2026):
The above is in FF, the below is what I see in the chrome console:
@Maddog0057 commented on GitHub (Jan 3, 2026):
Same issue after updating to v2. Tested using the code directly and the link, as well as with multiple user accounts.
@MrExplode commented on GitHub (Jan 4, 2026):
Experiencing the same, tested with multiple users. (on multiple browsers spread across multiple OSes)
@stonith404 commented on GitHub (Jan 4, 2026):
Thanks for reporting this, the cookie configuration was wrong, so the token was never set. This should be fixed in
v2.1.0which will be available in a few minutes.@deuts commented on GitHub (Jan 6, 2026):
I'm on v2.1.0 and this Send Email Login code does not work:
The Show Code Login Code appears to be working as well as the Email Login option.