🐛 Bug Report: Can't update any settings #59

New Issue

OVERLORD · 2025-10-06T23:59:42+03:00

OVERLORD commented

2025-10-06 23:59:42 +03:00

Originally created by @softmodded on GitHub.

Reproduction steps

I think something may have messed up during the update from 1.7 to latest, but I haven't noticed until now. All I did was pull the latest image, and I didn't see any errors during the first run after the update, which was a few hours ago.

Expected behavior

I should be able to update settings & log into applications

Actual Behavior

Various database errors occured

Pocket ID Version

v1.9.1 (latest)

Database

SQLite

OS and Environment

Docker compose on Ubuntu 20.04 behind Traefik

Log Output

Attempting to update any settings related to OIDC clients gives the following error:
Error #01: SQL logic error: no such column: requires_reauthentication (1)

Attempting to log into any services produces a similar-looking error: Error #01: SQL logic error: no such column: last_used_at (1)

Originally created by @softmodded on GitHub. ### Reproduction steps I think something may have messed up during the update from 1.7 to latest, but I haven't noticed until now. All I did was pull the latest image, and I didn't see any errors during the first run after the update, which was a few hours ago. ### Expected behavior I should be able to update settings & log into applications ### Actual Behavior Various database errors occured ### Pocket ID Version v1.9.1 (latest) ### Database SQLite ### OS and Environment Docker compose on Ubuntu 20.04 behind Traefik ### Log Output Attempting to update any settings related to OIDC clients gives the following error: `Error #01: SQL logic error: no such column: requires_reauthentication (1)` Attempting to log into any services produces a similar-looking error: `Error #01: SQL logic error: no such column: last_used_at (1)`

OVERLORD closed this issue

2025-10-06 23:59:43 +03:00

OVERLORD commented

2025-10-06 23:59:45 +03:00

@jaehong21 commented on GitHub:

I just manually psql dump from original database, then create new clean app and psql.
and copy the original data into new one to fix it.
must had some issue with DB schema migration while upgrading pocket-id.

@jaehong21 commented on GitHub: I just manually psql dump from original database, then create new clean app and psql. and copy the original data into new one to fix it. must had some issue with DB schema migration while upgrading pocket-id.

OVERLORD commented

2025-10-06 23:59:45 +03:00

@jaehong21 commented on GitHub:

Same.
I've also updated v1.7 -> v1.8 -> v1.9.1
when startup, having errors like below

{
"time":"2025-08-26T10:22:42.701734641Z",
"level":"ERROR",
"msg":"Job failed with error",
"app":"pocket-id",
"version":"1.9.1",
"name":"ClearReauthenticationTokens",
"id":"xxx",
"error":"failed to clean expired reauthentication tokens: ERROR: relation \"reauthentication_tokens\" does not exist (SQLSTATE 42P01)"}

still the server is accessible anyway.

But. when making any changes and try to save with OIDC clients. 500 happens with error log below

{
"time":"2025-08-26T10:25:56.268402482Z",
"level":"INFO",
"msg":"Error #01: invalid field",
"app":"pocket-id",
"version":"1.9.1",
"request":
{
"time":"2025-08-26T10:25:56.247583361Z",
"method":"PUT",
"host":"xxx",
"path":"/api/oidc/clients/xxx/allowed-user-groups",
"query":"",
"params":
{"id": "xxx"},
"route":
"/api/oidc/clients/:id/allowed-user-groups",
"ip":"xxx",
"referer":"xxx/settings/admin/oidc-clients/xxx","length":57},
"response":{"time":"2025-08-26T10:25:56.268371281Z","latency":20787920,"status":500,"length":32}}

@jaehong21 commented on GitHub: Same. I've also updated v1.7 -> v1.8 -> v1.9.1 when startup, having errors like below ```json { "time":"2025-08-26T10:22:42.701734641Z", "level":"ERROR", "msg":"Job failed with error", "app":"pocket-id", "version":"1.9.1", "name":"ClearReauthenticationTokens", "id":"xxx", "error":"failed to clean expired reauthentication tokens: ERROR: relation \"reauthentication_tokens\" does not exist (SQLSTATE 42P01)"} ``` still the server is accessible anyway. But. when making any changes and try to save with OIDC clients. 500 happens with error log below ```json { "time":"2025-08-26T10:25:56.268402482Z", "level":"INFO", "msg":"Error #01: invalid field", "app":"pocket-id", "version":"1.9.1", "request": { "time":"2025-08-26T10:25:56.247583361Z", "method":"PUT", "host":"xxx", "path":"/api/oidc/clients/xxx/allowed-user-groups", "query":"", "params": {"id": "xxx"}, "route": "/api/oidc/clients/:id/allowed-user-groups", "ip":"xxx", "referer":"xxx/settings/admin/oidc-clients/xxx","length":57}, "response":{"time":"2025-08-26T10:25:56.268371281Z","latency":20787920,"status":500,"length":32}} ```

OVERLORD commented

2025-10-06 23:59:46 +03:00

@stonith404 commented on GitHub:

I'm closing this because there was no response. Feel free to comment here if the issue still occurs.

@stonith404 commented on GitHub: I'm closing this because there was no response. Feel free to comment here if the issue still occurs.

OVERLORD commented

2025-10-06 23:59:46 +03:00

@stonith404 commented on GitHub:

Did you guys run anything manually on the database when you've upgraded to v1.7.0 because we had some db issues in this version?

@stonith404 commented on GitHub: Did you guys run anything manually on the database when you've upgraded to v1.7.0 because we had some db issues in this version?

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#59