Node screen broken after Headscale 0.28 upgrade - node data not displaying

[heinrichnak]

After upgrading to Headscale 0.28, the node screen in headscale-ui is no longer displaying node information correctly. While the UI elements are visible, all node data fields (ID, Device Name, Last Seen) are empty.
Environment:

Headscale version: 0.28
Headscale-ui version: 2025.08.23

Steps to Reproduce:

Upgrade Headscale to version 0.28
Access headscale-ui
Navigate to the Device View (nodes screen)
Observe that node data is not populated

Expected Behavior:
The nodes screen should display complete information for each registered node including:

Node ID
Device Name
Last Seen timestamp

Actual Behavior:
The node list shows empty rows with no data populated in the ID, Device Name, or Last Seen columns. Only UI elements like the "+ tag" button and action icons are visible.

Additional Context:
This issue appears to be caused by breaking changes in Headscale 0.28's API. The node screen worked correctly with Headscale 0.27 and earlier versions. This suggests the API response format or endpoint may have changed.

[drmedicu]

Same issue here. I reinstalled the docker etc and I am still not seeing the nodes anymore under device view

[wrenix]

JS-Console shows:

Uncaught (in promise) TypeError: can't access property Symbol.iterator, items is undefined
    Immutable 43

[CaffeinatedOpe]

Seeing the same behavior here. Also, the api key rollover function is now broken with a regex error in the logs.

[shaggyz]

Just chiming in to confirm this issue and provide the root cause!

I ran into this today on a fresh Headscale deployment. The API is returning the data correctly, but Headscale recently updated its terminology and API schema. It now returns the device list under the "nodes" key, whereas this UI codebase seems to be expecting the legacy "machines" array.

Because the expected array doesn't exist, the UI gets undefined and throws this in the browser console:
Unhandled Promise Rejection: TypeError: Array.from requires an array-like object - not null or undefined

Here is a truncated snippet of the current Headscale API response showing the new structure:

{
    "nodes": [
        {
            "id": "3",
            "name": "fermi",
            "ipAddresses": [
                "100.64.0.1"
            ],
            "online": true
        }
    ]
}

Suggested Fix:

Updating the frontend data parsing logic to use a fallback should safely support both the legacy and current Headscale API versions:

const devices = response.nodes || response.machines;

Hope this helps speed up a patch!

[hmic]

Just chiming in to confirm this issue and provide the root cause!

I ran into this today on a fresh Headscale deployment. The API is returning the data correctly, but Headscale recently updated its terminology and API schema. It now returns the device list under the "nodes" key, whereas this UI codebase seems to be expecting the legacy "machines" array.

Because the expected array doesn't exist, the UI gets undefined and throws this in the browser console: Unhandled Promise Rejection: TypeError: Array.from requires an array-like object - not null or undefined

...

Updating the frontend data parsing logic to use a fallback should safely support both the legacy and current Headscale API versions:

const devices = response.nodes || response.machines;

I am not sure which branch you are talking about, master does not contain the word "machines" even once! Btw. "const devices" neither.

With that your whole assessment - and fix - looks like AI slop.

The UI is expecting the correct/current "nodes" key in the API return.

You've got right that the structure of the node data in the API return has changed from 0.27 to 0.28.

[hehh2001]

Seeing the same behavior here. Also, the api key rollover function is now broken with a regex error in the logs.

[heinrichnak]

I am using headplane until there's a fix for headscale-ui. The latest version (0.26) now supports headscale 0.28.
I prefer headscale-ui though, because it is lightweight and it is all I need.

Not a developer, but maybe the fixes in headplane can help create a patch for headscale-ui.

[routerino]

I'll have a look this week, not the first time that headscale has broken their API on an update.