🐛 Bug Report: Can no longer login with my existing user on latest main #293

New Issue

OVERLORD · 2026-02-04T18:37:07+03:00

OVERLORD commented

2026-02-04 18:37:07 +03:00

Originally created by @antifuchs on GitHub (May 22, 2025).

Reproduction steps

Attempt to authenticate with my registered passkey
observe an authentication failure, backend logs say Error #01: Failed to lookup Client-side Discoverable Credential: record not found
Attempt to create a login code with pocket-id-create-one-time-access-token.sh db-file.db asf and use that emitted URL within 1 minute,
observe an authentication failure, backend logs say Error #01: token is invalid or expired

Expected behavior

I would expect the user that has existed & able to login for nearly 6 months to continue to be able to log in.

Actual Behavior

pocket-id is unable to authenticate me, using credentials that pocket-id is generating in its own database.

Version and Environment

Using rev d6104bbb35 triggers this issue.

Downgrading to release v0.53.0, the issue doesn't trigger. Could this be related to the sqlite driver refactor?

Log Output

No response

Originally created by @antifuchs on GitHub (May 22, 2025). ### Reproduction steps 1. Attempt to authenticate with my registered passkey 2. observe an authentication failure, backend logs say `Error #01: Failed to lookup Client-side Discoverable Credential: record not found` 3. Attempt to create a login code with `pocket-id-create-one-time-access-token.sh db-file.db asf` and use that emitted URL within 1 minute, 4. observe an authentication failure, backend logs say `Error #01: token is invalid or expired` ### Expected behavior I would expect the user that has existed & able to login for nearly 6 months to continue to be able to log in. ### Actual Behavior pocket-id is unable to authenticate me, using credentials that pocket-id is generating in its own database. ### Version and Environment Using rev d6104bbb351672e2b3d6aa2c09083359d0428d94 triggers this issue. Downgrading to release [v0.53.0](https://github.com/pocket-id/pocket-id/releases/tag/v0.53.0), the issue doesn't trigger. Could this be related to the sqlite driver refactor? ### Log Output _No response_

OVERLORD added the bug label 2026-02-04 18:37:07 +03:00

OVERLORD closed this issue

2026-02-04 18:37:10 +03:00

OVERLORD commented

2026-02-04 18:37:16 +03:00

@stonith404 commented on GitHub (May 22, 2025):

If you use the standalone installation we recommend that you don't use the latest commit on the main branch but the latest available tag.

The issue is probably caused by f1154257c5 which removes the deprecated environment variable SQLITE_DB_PATH which gets replaced by DB_CONNECTION_STRING. This change isn't documented yet because we haven't created the release yet.

@stonith404 commented on GitHub (May 22, 2025): If you use the standalone installation we recommend that you don't use the latest commit on the main branch but the latest available tag. The issue is probably caused by f1154257c5a9ac5c95d81343a31c02251631b203 which removes the deprecated environment variable `SQLITE_DB_PATH` which gets replaced by [`DB_CONNECTION_STRING`](https://pocket-id.org/docs/configuration/environment-variables/#database-connection-string). This change isn't documented yet because we haven't created the release yet.

OVERLORD referenced this issue

2026-02-04 20:48:56 +03:00

[PR #293] [MERGED] ci/cd: add pr docker build #712

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/pocket-id#293