[GH-ISSUE #913] Next Auth fetch failed #600

Closed
opened 2026-03-02 11:51:13 +03:00 by kerem · 2 comments
Owner

Originally created by @LukanRocks on GitHub (Jan 20, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/913

Describe the Bug

I'm seeing this error on the logs:

hoarder | [next-auth][error][CLIENT_FETCH_ERROR]
hoarder | https://next-auth.js.org/errors#client_fetch_error fetch failed {
hoarder | error: {
hoarder | message: 'fetch failed',
hoarder | stack: 'TypeError: fetch failed\n' +
hoarder | ' at node:internal/deps/undici/undici:13484:13\n' +
hoarder | ' at process.processTicksAndRejections (node:internal/process/task_queues:105:5)',
hoarder | name: 'TypeError'
hoarder | },
hoarder | url: 'https://hoarder.homeserver.lukan.rocks/api/auth/providers',
hoarder | message: 'fetch failed'
hoarder | }

Steps to Reproduce

I'm just trying to login.

My compose file:
`
secrets:
hoarder_nextauth:
file: $DOCKER_SECRETS_DIR/hoarder_nextauth
meili_master_key:
file: $DOCKER_SECRETS_DIR/meili_master_key

services:
hoarder:
container_name: hoarder
image: ghcr.io/hoarder-app/hoarder:release
restart: unless-stopped
security_opt:
- no-new-privileges:true
volumes:
- $DOCKER_DATA_DIR/hoarder:/data
secrets:
- hoarder_nextauth
- meili_master_key
environment:
TZ: $TZ
DATA_DIR: /data
DISABLE_SIGNUPS: true
NEXTAUTH_SECRET: /run/secrets/hoarder_nextauth
NEXTAUTH_URL: https://hoarder.homeserver.lukan.rocks
MEILI_ADDR: http://meilisearch:7700
MEILI_MASTER_KEY: /run/secrets/meili_master_key
BROWSER_WEB_URL: http://chrome:9222
# OPENAI_API_KEY: look ollama implementation
depends_on:
- traefik
- chrome
- meilisearch
networks:
- traefik-proxy
labels:
- traefik.enable=true
- traefik.http.routers.hoarder-router.rule=Host(hoarder.homeserver.lukan.rocks)
- traefik.http.routers.hoarder-router.entrypoints=web,websecure
- traefik.http.routers.hoarder-router.tls=true
- traefik.http.routers.hoarder-router.tls.certresolver=letsencrypt
- traefik.http.routers.hoarder-router.service=hoarder-service
- traefik.http.services.hoarder-service.loadbalancer.server.port=3000

chrome:
container_name: chrome
image: gcr.io/zenika-hub/alpine-chrome:123
restart: unless-stopped
security_opt:
- no-new-privileges:true
depends_on:
- traefik
networks:
- traefik-proxy
command:
- --no-sandbox
- --disable-gpu
- --disable-dev-shm-usage
- --remote-debugging-address=0.0.0.0
- --remote-debugging-port=9222
- --hide-scrollbars

meilisearch:
container_name: meilisearch
image: getmeili/meilisearch:v1.11.1
restart: unless-stopped
security_opt:
- no-new-privileges:true
depends_on:
- traefik
networks:
- traefik-proxy
volumes:
- $DOCKER_DATA_DIR/meilisearch:/meili_data
secrets:
- meili_master_key
environment:
MEILI_NO_ANALYTICS: true
MEILI_MASTER_KEY: /run/secrets/meili_master_key`

Expected Behaviour

Not have this error.

Screenshots or Additional Context

No response

Device Details

Ubuntu Server with Docker Compose

Exact Hoarder Version

:latest sha256:0a947528917e1cd6055943affb7c2476ca7efd4a01f386bda59f13eee155c85c

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 @LukanRocks on GitHub (Jan 20, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/913 ### Describe the Bug I'm seeing this error on the logs: hoarder | [next-auth][error][CLIENT_FETCH_ERROR] hoarder | https://next-auth.js.org/errors#client_fetch_error fetch failed { hoarder | error: { hoarder | message: 'fetch failed', hoarder | stack: 'TypeError: fetch failed\n' + hoarder | ' at node:internal/deps/undici/undici:13484:13\n' + hoarder | ' at process.processTicksAndRejections (node:internal/process/task_queues:105:5)', hoarder | name: 'TypeError' hoarder | }, hoarder | url: 'https://hoarder.homeserver.lukan.rocks/api/auth/providers', hoarder | message: 'fetch failed' hoarder | } ### Steps to Reproduce I'm just trying to login. My compose file: ` secrets: hoarder_nextauth: file: $DOCKER_SECRETS_DIR/hoarder_nextauth meili_master_key: file: $DOCKER_SECRETS_DIR/meili_master_key services: hoarder: container_name: hoarder image: ghcr.io/hoarder-app/hoarder:release restart: unless-stopped security_opt: - no-new-privileges:true volumes: - $DOCKER_DATA_DIR/hoarder:/data secrets: - hoarder_nextauth - meili_master_key environment: TZ: $TZ DATA_DIR: /data DISABLE_SIGNUPS: true NEXTAUTH_SECRET: /run/secrets/hoarder_nextauth NEXTAUTH_URL: https://hoarder.homeserver.lukan.rocks MEILI_ADDR: http://meilisearch:7700 MEILI_MASTER_KEY: /run/secrets/meili_master_key BROWSER_WEB_URL: http://chrome:9222 # OPENAI_API_KEY: look ollama implementation depends_on: - traefik - chrome - meilisearch networks: - traefik-proxy labels: - traefik.enable=true - traefik.http.routers.hoarder-router.rule=Host(`hoarder.homeserver.lukan.rocks`) - traefik.http.routers.hoarder-router.entrypoints=web,websecure - traefik.http.routers.hoarder-router.tls=true - traefik.http.routers.hoarder-router.tls.certresolver=letsencrypt - traefik.http.routers.hoarder-router.service=hoarder-service - traefik.http.services.hoarder-service.loadbalancer.server.port=3000 chrome: container_name: chrome image: gcr.io/zenika-hub/alpine-chrome:123 restart: unless-stopped security_opt: - no-new-privileges:true depends_on: - traefik networks: - traefik-proxy command: - --no-sandbox - --disable-gpu - --disable-dev-shm-usage - --remote-debugging-address=0.0.0.0 - --remote-debugging-port=9222 - --hide-scrollbars meilisearch: container_name: meilisearch image: getmeili/meilisearch:v1.11.1 restart: unless-stopped security_opt: - no-new-privileges:true depends_on: - traefik networks: - traefik-proxy volumes: - $DOCKER_DATA_DIR/meilisearch:/meili_data secrets: - meili_master_key environment: MEILI_NO_ANALYTICS: true MEILI_MASTER_KEY: /run/secrets/meili_master_key` ### Expected Behaviour Not have this error. ### Screenshots or Additional Context _No response_ ### Device Details Ubuntu Server with Docker Compose ### Exact Hoarder Version :latest sha256:0a947528917e1cd6055943affb7c2476ca7efd4a01f386bda59f13eee155c85c ### 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:51:13 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

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

This was fixed in the nightly build. Given that you are already on nightly maybe try updating?

If not, you can also try adding:

NEXTAUTH_URL_INTERNAL=http://localhost:3000

in the env file and this error will disappear.

<!-- gh-comment-id:2601938484 --> @MohamedBassem commented on GitHub (Jan 20, 2025): This was fixed in the nightly build. Given that you are already on nightly maybe try updating? If not, you can also try adding: NEXTAUTH_URL_INTERNAL=http://localhost:3000 in the env file and this error will disappear.
Author
Owner

@MohamedBassem commented on GitHub (Feb 16, 2025):

This has been released in the stable release

<!-- gh-comment-id:2661624678 --> @MohamedBassem commented on GitHub (Feb 16, 2025): This has been released in the stable release
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#600
No description provided.