Incompatibility with Headscale 0.26.1 – preauthkey requires numeric user ID instead of username

[jecabe]

I’m testing headscale-admin against Headscale 0.26.1. The UI mostly works, but creating or listing preauthkeys fails with a 400 Bad Request error.

Details

Headscale version: 0.26.1

headscale-admin version: v0.25.6 (admin.zip release)

Environment: Debian 12 + Caddy proxy

API URL configured in UI: http://IP/api

HRGET http://192.168.1.250/api/v1/preauthkey?user=MYUSER
[HTTP/1.1 400 Bad Request 55ms]

Uncaught (in promise) Error: parsing field "user": strconv.ParseUint: parsing "MYUSER": invalid syntax

Observation

In Headscale 0.26.1, the /api/v1/preauthkey endpoints still expect the user field to be a numeric ID (e.g. 1), not the username.

For example, with the CLI:

headscale preauthkeys create --user 1 --reusable

works, but

headscale preauthkeys create --user MYUSER

fails with the same parsing error.

Expected behavior

The UI should either:

• Detect that Headscale 0.26.x requires user= and use the numeric ID, or
• Clearly document that headscale-admin requires a newer Headscale version where username is supported.

[hutchYy]

Hey,

Having same issue here.
Preauth keys can't be fetch, added, modified as the headscale numeric user id is now used instead of the user string.

Have a good day :)

[GoodiesHQ]

Hello, the 0.26 branch is the correct branch to use for 0.26. I always keep the major version of headscale-admin inline with headscale for guaranteed compatibility, so if you want it to be compatible with headscale 0.25, use headscale-admin 0.25. If you want headscale 0.26, use headscale-admin 0.26, etc.

The minor version is not in sync, but doesn't need to be as headscale won't introduce breaking changes within a single version. Let me know if you have any issues. I think I just forgot to push a 0.26 release several months back when I last pushed it, but it is merged with main and it does have its own docker image:

https://hub.docker.com/layers/goodieshq/headscale-admin/0.26/