Linkwarden widget in Homepage does not support JWT tokens from latest Linkwarden

[newsqualychen]

Description

Homepage's Linkwarden widget fails to connect when using the latest Linkwarden (v3+) Access Tokens (JWT starting with "eyJ...").

• The token works with curl directly against the API:
  curl -H "Authorization: Bearer eyJ..." http://10.10.10.226:3008/api/v1/collections
• Homepage widget configured like this fails:
  • linkwarden:
    icon: linkwarden.webp
    href: http://10.10.10.226:3008
    widget:
    type: linkwarden
    url: http://10.10.10.226:3008
    key: eyJhbGciOiJ...
• Error shown: "API Error: connect ETIMEDOUT 10.10.10.226:3008"
• Environment:
  • Homepage version: latest (Docker)
  • Linkwarden version: v3+ (Docker)
  • Ubuntu 22.04, Docker 24

Expected: Homepage should accept JWT tokens generated by the latest Linkwarden and display collections correctly.

Notes: This seems to be a compatibility issue, as Homepage currently only supports the old lw_ style API tokens.

homepage version

v1.10.1 (0ce175c,

Installation method

Docker

Configuration

- linkwarden:
      icon: linkwarden.webp
      href: http://10.10.10.226:3008
      widget:
        type: linkwarden
        url: http://10.10.10.226:3008
        key: eyJhbGciOiJ...

Container Logs

  at <unknown> (Error: connect ETIMEDOUT 10.10.10.226:3008) {

errno: -110,

code: 'ETIMEDOUT',

syscall: 'connect',

address: '10.10.10.226',

port: 3008

}

]

[2026-02-23T01:36:37.034Z] error: HTTP Error 500 calling http://10.10.10.226:3008/api/v1/collections

[2026-02-23T01:36:37.036Z] error: Error calling http://10.10.10.226:3008/api/v1/tags...

[2026-02-23T01:36:37.036Z] error: [

500,

Error: connect ETIMEDOUT 10.10.10.226:3008

  at <unknown> (Error: connect ETIMEDOUT 10.10.10.226:3008) {

errno: -110,

code: 'ETIMEDOUT',

syscall: 'connect',

address: '10.10.10.226',

port: 3008

}

]

[2026-02-23T01:36:37.037Z] error: HTTP Error 500 calling http://10.10.10.226:3008/api/v1/tags

[2026-02-23T01:40:54.513Z] error: Error calling http://10.10.10.225:2283/api/server/version...

[2026-02-23T01:40:54.514

Browser Logs

No response

Troubleshooting

Issue Summary:
The Linkwarden widget in Homepage fails to connect when using the latest Linkwarden (v3+) Access Tokens, which are JWT tokens starting with "eyJ...".

Steps Taken to Troubleshoot:

1. Verified Linkwarden is running and accessible:
   curl http://10.10.10.226:3008/api/v1/collections
   Response: {"response":"You must be logged in."} (expected for unauthenticated requests)

2. Tested the JWT token directly:
   curl -H "Authorization: Bearer eyJ..." http://10.10.10.226:3008/api/v1/collections
   Response: JSON data successfully returned.
   ✅ This confirms the token is valid and the API works.

3. Configured Homepage widget in services.yaml:

• linkwarden:
  icon: linkwarden.webp
  href: http://10.10.10.226:3008
  widget:
  type: linkwarden
  url: http://10.10.10.226:3008
  key: eyJhbGciOiJ...

4. Restarted Homepage container:
   docker restart homepage

Observed Behavior:

• Homepage shows API connection errors (ETIMEDOUT or failed to fetch collections)
• Widget fails to display collections despite the token being valid

Expected Behavior:

• Homepage should accept JWT tokens generated by the latest Linkwarden and display collections correctly

Environment:

• Homepage version: latest (Docker)
• Linkwarden version: v3+ (Docker)
• Server OS: Ubuntu 22.04, Docker 24
• Network: homepage and linkwarden on same network / reachable via IP

Notes:

• This appears to be a compatibility issue: Homepage only supports the old lw_ style API tokens.
• Using account username/password works as a workaround with the latest Linkwarden.

[shamoon]

There’s literally no mention of it in their release notes. Assuming it’s a breaking change it would have to eventually be handled on our side by the homepage widget.

that said, the suspicious thing about your report is that your curl suggests no change to how the key is expected and that’s what we already do:

homepage/src/utils/proxy/handlers/credentialed.js

Line 61 in 614a87d

"linkwarden",

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.