v0.12.0-beta2

[henrygd]

Warning

This is a beta release. Please make a hub backup before upgrading.

• Add 5 and 15 minute load average to systems table (feat: LA, migration, float alert value, manual alert value input #816)
• Add alerts for load average (thanks @Allespro)
• Fix issue with multiple systems using the same token

For more information about new features in 0.12.0, see the 0.12.0-beta1 release notes.

Please report issues or provide feedback in #951. Thanks!

Upgrading

• Docker: Switch to the :edge tag.
• Other: Download the new binary, replace the old one, then add the new env vars and restart the service.

For those running the Linux agent binary, the copy/paste install command in the hub should work if you add -v "0.12.0-beta2" to the script arguments.

Full Changelog: v0.12.0-beta1...v0.12.0-beta2

[eddively]

The code feature sounds fantastic.

[svenvg93]

The hub and agent installed flawlessly, and everything’s happily running over WebSockets—thank you for this fantastic improvement! 😄

One quick suggestion: could we display the current connection type (SSH vs. WebSocket) somewhere in the hub—say, as a tooltip on the agent version or in PocketBase—and maybe even trigger an alert when it switches between methods?

[djakupovic]

just tried the beta version. the agent does not connect to the hub with the universal token, tried several restarts. I replaced then the binary like you said. the first host connected.
with the same token I tried another host but after the replacement it did not connect:
Jul 10 20:35:29 docker2 systemd[1]: Started beszel-agent.service - Beszel Agent Service. Jul 10 20:35:29 docker2 beszel-agent[589655]: 2025/07/10 20:35:29 INFO Data directory path=/var/lib/beszel-agent Jul 10 20:35:29 docker2 beszel-agent[589655]: 2025/07/10 20:35:29 INFO Detected root device name=dm-6 Jul 10 20:35:29 docker2 beszel-agent[589655]: 2025/07/10 20:35:29 INFO Detected network interface name=eth0 sent=1047350213 recv=3975799937 Jul 10 20:35:29 docker2 beszel-agent[589655]: 2025/07/10 20:35:29 INFO WebSocket connected host=beszel.domain.com Jul 10 20:35:29 docker2 beszel-agent[589655]: 2025/07/10 20:35:29 WARN Connection closed err="connection closed, code=1000, reason=" Jul 10 20:35:29 docker2 beszel-agent[589655]: 2025/07/10 20:35:29 WARN Disconnected from hub

Afterwards I restarted the hub to get a new token and redid everything, then it could connect. So the same token does not work twice it seems

[svenvg93]

The universal token expires after an hour—maybe that’s what happened?
@henrygd, is there a way to keep it from expiring? These tokens will mostly be used for automation, so it’d be a hassle if they expire quickly or reset on reboot.

[djakupovic]

Thank you for the reply, no the token was used within 3 minutes again by another host. I needed to restart in order to get another token because the token could not be used twice.
the log in the database just says: "fingerprint mismatch" when I used the token for more than 1 agent

[henrygd]

Probably a bug, I'll look further into it.

If it's an existing system you can copy or rotate the current token in the table on the token settings page. Otherwise manually adding with the 'add system' dialog will generate a unique token.

[henrygd]

It was a bug. It doesn't affect security so you're fine to keep running the beta.

Edit: Should be fixed now in v0.12.0-beta2

[freddong]

It's not fixed in 0.12.10, when I use ansible to install to 8 hosts, only few of them can be seen on dashboard.

The log from one of the failed host:
beszel-agent[3248454]: 2025/09/23 16:34:01 INFO WebSocket connected host=XXX
beszel-agent[3248454]: 2025/09/23 16:34:01 WARN Connection closed err="connection closed, code=1000, reason="
beszel-agent[3248454]: 2025/09/23 16:34:01 WARN Disconnected from hub
beszel-agent[3248454]: 2025/09/23 16:34:06 INFO WebSocket connected host=XXX
beszel-agent[3248454]: 2025/09/23 16:34:06 WARN Connection closed err="connection closed, code=1000, reason="
beszel-agent[3248454]: 2025/09/23 16:34:06 WARN Disconnected from hub

[a-mnich]

The new v0.12.0-beta2 is missing the edge tag on the images. I've submitted a PR that should fix it for future releases.

@henrygd Can you manually tag the v0.12.0-beta2 images with the edge tag?

[henrygd]

Thanks, the edge tags should be updated now.

[svenvg93]

Found a bug for the Load Average, sometimes the value is empty on the system table.

This not present in the System stat either, l15 and l5 are missing here.

{
  "cpu": 0.59,
  "m": 3.7,
  "mu": 0.3,
  "mp": 8,
  "mb": 2.85,
  "s": 0.5,
  "d": 28.82,
  "du": 6.21,
  "dp": 22.71,
  "dr": 0,
  "dw": 0.02,
  "ns": 0,
  "nr": 0,
  "t": {
    "cpu_thermal": 37.97
  }
}

I do see it in older stats, suspecting it is because we omitzero

beszel/beszel/internal/entities/system/system.go

Lines 34 to 36 in 806c4e5

	LoadAvg1 float64 `json:"l1,omitempty" cbor:"23,keyasint,omitempty,omitzero"`
	LoadAvg5 float64 `json:"l5,omitempty" cbor:"24,keyasint,omitempty,omitzero"`
	LoadAvg15 float64 `json:"l15,omitempty" cbor:"25,keyasint,omitempty,omitzero"`

If you want I can fix it as part of #960

[henrygd]

Sure, thanks. Let's remove omitzero.

[svenvg93]

It's been removed in that PR.

[pxlvoid]

When installing on windows first time:

Firewall rule created successfully.
Starting beszel-agent service...
beszel-agent: Unexpected status SERVICE_START_PENDING in response to START control.
NSSM start command returned error code: 1
This could be due to 'SERVICE_START_PENDING' state. Checking service status...
Success! The beszel-agent service is now running.

When second time:
Success! The beszel-agent service is running properly.

Also you should use " when generating url for mac because of globbing (zsh).

No luck installing on Windows or Mac. Not automatically registered in hub.