starred/karakeep

Fork 0

mirror of https://github.com/karakeep-app/karakeep.git synced 2026-04-26 08:26:03 +03:00

[GH-ISSUE #1711] Users created using Pocket-ID OIDC cause server crash #1066

New issue

Closed

opened 2026-03-02 11:54:45 +03:00 by kerem · 2 comments

kerem commented

2026-03-02 11:54:45 +03:00

Owner

Originally created by @jeliebold on GitHub (Jul 8, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1711

Describe the Bug

I setup Karakeep v0.25.0 on Ubuntu 24.04.2 LTS using default docker compose settings, adding only OIDC settings for integration with Pocket ID.
I made a local Admin user by making a password signin
When I login with a different user through OIDC, karakeep creates an account for the user, but the server throws an error. See below.

Server Error:
Application error: a server-side exception has occurred (see the server logs for more information). Digest: 4237581454

Other info:

If I login with OIDC for an existing user using "OAUTH_ALLOW_DANGEROUS_EMAIL_ACCOUNT_LINKING", it seems to work fine.
Using Pangolin as reverse proxy / security.
Composer, ENV, and Log of signin attached.

I've used Karakeep without OIDC and really like it. Thank you for all the effort put into this!

karakeep-compose.txt
karakeep-env2.txt
karakeep-log.txt

Steps to Reproduce

Setup Karakeep v0.25.0 on Ubuntu 24.04.2 LTS using default docker compose setting, adding only OIDC setting for integration with Pocket ID.
Make local admin account.
Login using OIDC with user that does not have account on Karakeep.
Server throws error Application error: a server-side exception has occurred (see the server logs for more information). Digest: 4237581454

Expected Behaviour

OIDC login should create new user account and successfully login.

Screenshots or Additional Context

Device Details

Edge and Chrome on Windows 10

Exact Karakeep Version

v0.25.0

Have you checked the troubleshooting guide?

I have checked the troubleshooting guide and I haven't found a solution to my problem

Originally created by @jeliebold on GitHub (Jul 8, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1711 ### Describe the Bug 1. I setup Karakeep v0.25.0 on Ubuntu 24.04.2 LTS using default docker compose settings, adding only OIDC settings for integration with Pocket ID. 2. I made a local Admin user by making a password signin 3. When I login with a different user through OIDC, karakeep creates an account for the user, but the server throws an error. See below. **Server Error:** `Application error: a server-side exception has occurred (see the server logs for more information). Digest: 4237581454` **Other info:** - If I login with OIDC for an existing user using "OAUTH_ALLOW_DANGEROUS_EMAIL_ACCOUNT_LINKING", it seems to work fine. - Using Pangolin as reverse proxy / security. - Composer, ENV, and Log of signin attached. I've used Karakeep without OIDC and really like it. Thank you for all the effort put into this! [karakeep-compose.txt](https://github.com/user-attachments/files/21112748/karakeep-compose.txt) [karakeep-env2.txt](https://github.com/user-attachments/files/21112836/karakeep-env2.txt) [karakeep-log.txt](https://github.com/user-attachments/files/21112750/karakeep-log.txt) ### Steps to Reproduce 1. Setup Karakeep v0.25.0 on Ubuntu 24.04.2 LTS using default docker compose setting, adding only OIDC setting for integration with Pocket ID. 2. Make local admin account. 3. Login using OIDC with user that does not have account on Karakeep. 4. Server throws error `Application error: a server-side exception has occurred (see the server logs for more information). Digest: 4237581454` ### Expected Behaviour OIDC login should create new user account and successfully login. ### Screenshots or Additional Context <img width="805" height="194" alt="Image" src="https://github.com/user-attachments/assets/0125bbea-6978-4942-8069-b529415efc8c" /> ### Device Details Edge and Chrome on Windows 10 ### Exact Karakeep Version v0.25.0 ### Have you checked the troubleshooting guide? - [x] I have checked the troubleshooting guide and I haven't found a solution to my problem

kerem

2026-03-02 11:54:45 +03:00

closed this issue
added the
bug

status/untriaged
labels

kerem commented

2026-03-02 11:54:46 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Jul 8, 2025):

hey sorry for the hassle. This was a bug in 0.25 which is now fixed in the nightly build and the fix will be released in 0.26. As a workaround, you can create the account first before linking it with oauth and it'll work.

@MohamedBassem commented on GitHub (Jul 8, 2025): hey sorry for the hassle. This was a bug in 0.25 which is now fixed in the nightly build and the fix will be released in 0.26. As a workaround, you can create the account first before linking it with oauth and it'll work.

kerem commented

2026-03-02 11:54:46 +03:00

Author

Owner

@jeliebold commented on GitHub (Jul 9, 2025):

Hey Mohamed, thanks for the response! Glad to hear you have a fix in the works. I appreciate all the effort put into this project.

@jeliebold commented on GitHub (Jul 9, 2025): Hey Mohamed, thanks for the response! Glad to hear you have a fix in the works. I appreciate all the effort put into this project.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/karakeep#1066

No description provided.

Rows
Columns