[GH-ISSUE #2051] Previously working OIDC login fails with error: OAuth login failed: undefined #1277

Open
opened 2026-03-02 11:56:14 +03:00 by kerem · 3 comments
Owner

Originally created by @willyp713 on GitHub (Oct 17, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2051

Describe the Bug

Previously working install, now doesn't allow any logins, whether by password (if I re-enable password login) or by OIDC. Every login attempt redirects to https://my.site/signin?error=undefined and displays the error message: OAuth login failed: undefined

Using Pocket ID v1.13.1 for OAuth

Deployed config:

      DISABLE_PASSWORD_AUTH: "true"
      DISABLE_SIGNUPS: "true"
      KARAKEEP_VERSION: latest
      NEXTAUTH_URL: https://my.site
      OAUTH_ALLOW_DANGEROUS_EMAIL_ACCOUNT_LINKING: "true"
      OAUTH_CLIENT_ID: redacted
      OAUTH_CLIENT_SECRET: redacted
      OAUTH_PROVIDER_NAME: SSO
      OAUTH_WELLKNOWN_URL: https://myauth.site/.well-known/openid-configuration

Steps to Reproduce

  1. Go to sign in page
  2. Click the button for OAuth / OIDC single sign on
  3. Login fails and returns to sign-in screen with error `OAuth login failed: undefined'

Expected Behaviour

Should allow login into karakeep

Screenshots or Additional Context

Image

Device Details

Arc Version 1.75.0.223 (0000) Chromium Engine Version 141.0.7390.66 on Windows 11

Exact Karakeep Version

0.27.1

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 @willyp713 on GitHub (Oct 17, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2051 ### Describe the Bug Previously working install, now doesn't allow any logins, whether by password (if I re-enable password login) or by OIDC. **Every** login attempt redirects to `https://my.site/signin?error=undefined` and displays the error message: `OAuth login failed: undefined` Using Pocket ID v1.13.1 for OAuth Deployed config: ```YAML DISABLE_PASSWORD_AUTH: "true" DISABLE_SIGNUPS: "true" KARAKEEP_VERSION: latest NEXTAUTH_URL: https://my.site OAUTH_ALLOW_DANGEROUS_EMAIL_ACCOUNT_LINKING: "true" OAUTH_CLIENT_ID: redacted OAUTH_CLIENT_SECRET: redacted OAUTH_PROVIDER_NAME: SSO OAUTH_WELLKNOWN_URL: https://myauth.site/.well-known/openid-configuration ``` ### Steps to Reproduce 1. Go to sign in page 2. Click the button for OAuth / OIDC single sign on 3. Login fails and returns to sign-in screen with error `OAuth login failed: undefined' ### Expected Behaviour Should allow login into karakeep ### Screenshots or Additional Context <img width="504" height="526" alt="Image" src="https://github.com/user-attachments/assets/076d5e31-ab18-4b98-b02a-33fa01590c8a" /> ### Device Details Arc Version 1.75.0.223 (0000) Chromium Engine Version 141.0.7390.66 on Windows 11 ### Exact Karakeep Version 0.27.1 ### Have you checked the troubleshooting guide? - [x] I have checked the troubleshooting guide and I haven't found a solution to my problem
Author
Owner

@MohamedBassem commented on GitHub (Oct 20, 2025):

Anything in the web container logs when you get this error?

<!-- gh-comment-id:3420163374 --> @MohamedBassem commented on GitHub (Oct 20, 2025): Anything in the web container logs when you get this error?
Author
Owner

@willyp713 commented on GitHub (Oct 20, 2025):

Anything in the web container logs when you get this error?

I don't see anything. I just started the stack and tried to login as soon as the web server was up and this is all the web container shows:

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service init-db-migration: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-db-migration successfully started
s6-rc: info: service svc-workers: starting
s6-rc: info: service svc-web: starting
s6-rc: info: service svc-workers successfully started
s6-rc: info: service svc-web successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
Running db migration script
   ▲ Next.js 15.3.3
   - Local:        http://localhost:3000
   - Network:      http://0.0.0.0:3000

 ✓ Starting...
 ✓ Ready in 446ms
2025-10-20T01:41:49.131Z info: Plugins (Last one wins):
2025-10-20T01:41:49.158Z info:   search:
2025-10-20T01:41:49.158Z info:     - MeiliSearch
2025-10-20T01:41:49.158Z info:   queue:
2025-10-20T01:41:49.159Z info:     - Liteque
2025-10-20T01:41:50.605Z info: Plugins (Last one wins):
2025-10-20T01:41:50.606Z info:   search:
2025-10-20T01:41:50.606Z info:     - MeiliSearch
2025-10-20T01:41:50.606Z info:   queue:
2025-10-20T01:41:50.607Z info:     - Liteque
2025-10-20T01:41:51.368Z info: Workers version: nightly
2025-10-20T01:41:51.376Z info: [crawler] Loading adblocker ...
2025-10-20T01:41:51.376Z info: Starting inference worker ...
2025-10-20T01:41:51.377Z info: Starting search indexing worker ...
2025-10-20T01:41:51.377Z info: Starting tidy assets worker ...
2025-10-20T01:41:51.377Z info: Starting video worker ...
2025-10-20T01:41:51.378Z info: Starting feed worker ...
2025-10-20T01:41:51.378Z info: Starting asset preprocessing worker ...
2025-10-20T01:41:51.378Z info: Starting webhook worker ...
2025-10-20T01:41:51.378Z info: Starting rule engine worker ...
2025-10-20T01:41:51.383Z info: Listening on http://127.0.0.1:43275
2025-10-20T01:41:52.659Z info: [Crawler] Connecting to existing browser instance: http://chrome:9222
2025-10-20T01:41:52.660Z info: [Crawler] Successfully resolved IP address, new address: http://172.18.0.28:9222/
2025-10-20T01:41:52.718Z info: Starting crawler worker ...
2025-10-20T01:41:52.718Z info: [Crawler] Not defined in the server configuration BROWSER_COOKIE_PATH
2025-10-20T01:41:52.871Z info: <-- GET /api/health
2025-10-20T01:41:52.876Z info: --> GET /api/health 200 4ms
2025-10-20T01:42:22.941Z info: <-- GET /api/health
2025-10-20T01:42:22.942Z info: --> GET /api/health 200 1ms
2025-10-20T01:42:52.995Z info: <-- GET /api/health
2025-10-20T01:42:52.996Z info: --> GET /api/health 200 1ms
<!-- gh-comment-id:3420235564 --> @willyp713 commented on GitHub (Oct 20, 2025): > Anything in the web container logs when you get this error? I don't see anything. I just started the stack and tried to login as soon as the web server was up and this is all the web container shows: ``` s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service init-db-migration: starting s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service init-db-migration successfully started s6-rc: info: service svc-workers: starting s6-rc: info: service svc-web: starting s6-rc: info: service svc-workers successfully started s6-rc: info: service svc-web successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started Running db migration script ▲ Next.js 15.3.3 - Local: http://localhost:3000 - Network: http://0.0.0.0:3000 ✓ Starting... ✓ Ready in 446ms 2025-10-20T01:41:49.131Z info: Plugins (Last one wins): 2025-10-20T01:41:49.158Z info: search: 2025-10-20T01:41:49.158Z info: - MeiliSearch 2025-10-20T01:41:49.158Z info: queue: 2025-10-20T01:41:49.159Z info: - Liteque 2025-10-20T01:41:50.605Z info: Plugins (Last one wins): 2025-10-20T01:41:50.606Z info: search: 2025-10-20T01:41:50.606Z info: - MeiliSearch 2025-10-20T01:41:50.606Z info: queue: 2025-10-20T01:41:50.607Z info: - Liteque 2025-10-20T01:41:51.368Z info: Workers version: nightly 2025-10-20T01:41:51.376Z info: [crawler] Loading adblocker ... 2025-10-20T01:41:51.376Z info: Starting inference worker ... 2025-10-20T01:41:51.377Z info: Starting search indexing worker ... 2025-10-20T01:41:51.377Z info: Starting tidy assets worker ... 2025-10-20T01:41:51.377Z info: Starting video worker ... 2025-10-20T01:41:51.378Z info: Starting feed worker ... 2025-10-20T01:41:51.378Z info: Starting asset preprocessing worker ... 2025-10-20T01:41:51.378Z info: Starting webhook worker ... 2025-10-20T01:41:51.378Z info: Starting rule engine worker ... 2025-10-20T01:41:51.383Z info: Listening on http://127.0.0.1:43275 2025-10-20T01:41:52.659Z info: [Crawler] Connecting to existing browser instance: http://chrome:9222 2025-10-20T01:41:52.660Z info: [Crawler] Successfully resolved IP address, new address: http://172.18.0.28:9222/ 2025-10-20T01:41:52.718Z info: Starting crawler worker ... 2025-10-20T01:41:52.718Z info: [Crawler] Not defined in the server configuration BROWSER_COOKIE_PATH 2025-10-20T01:41:52.871Z info: <-- GET /api/health 2025-10-20T01:41:52.876Z info: --> GET /api/health 200 4ms 2025-10-20T01:42:22.941Z info: <-- GET /api/health 2025-10-20T01:42:22.942Z info: --> GET /api/health 200 1ms 2025-10-20T01:42:52.995Z info: <-- GET /api/health 2025-10-20T01:42:52.996Z info: --> GET /api/health 200 1ms ```
Author
Owner

@willyp713 commented on GitHub (Oct 20, 2025):

I noticed in the logs for Pocket ID that I'm not seeing Karakeep show up as a referrer anywhere. So it seems it's not properly reaching out to Pocket ID for the OAuth request. I checked a few other apps to be sure and they showed up in the Pocket ID logs immediately, as expected.

<!-- gh-comment-id:3420245128 --> @willyp713 commented on GitHub (Oct 20, 2025): I noticed in the logs for Pocket ID that I'm not seeing Karakeep show up as a referrer anywhere. So it seems it's not properly reaching out to Pocket ID for the OAuth request. I checked a few other apps to be sure and they showed up in the Pocket ID logs immediately, as expected.
Sign in to join this conversation.
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#1277
No description provided.