Weik.io 2026.2.4
A backup of a hub on several servers now keeps the record of which agent credentials were withdrawn on any of its servers. Each hub server also limits the memory that arriving telemetry batches can use.
Highlights
Backups
On a hub on several servers, weikio-backend backup collects each message server's copy of the list of withdrawn agent credentials and archives the newest one. The archive's sealed index records whether the backup collected a copy. When no copy arrives, or a key file can't be read, the backup archives the server's own list and prints one line about it on standard error.
Restore
A restore that writes an archive's keys prints one line on what the archive's index records about that list. When the archive may lack a withdrawal, the line advises you to restore an archive whose index says the backup collected a copy. The restore refuses none of these archives, because the archive you have may be the only one.
Telemetry
Each hub server accepts at most four telemetry batches arriving at once, which is at most 32 MiB of memory at the default batch limit. A batch that finds no place within two seconds gets 503 with Retry-After 5, and its sender sends it again. Before 2026.2.4 a server read every arriving batch whole into memory, so anyone with an ingest credential could use up its memory.
Fixes
- On a hub on several servers, a backup archived only the withdrawal list of the server it ran on. A hub restored from such an archive accepted the credentials withdrawn on the other servers again, such as an agent bundle that a re-issue replaced. 2026.2.0 to 2026.2.3 have the same fault. To restore a hub on several servers, use an archive whose sealed index says the backup collected a copy.
- On a hub on several servers, a withdrawal could be lost from every server after an upgrade that signs no new account token, such as an upgrade run again after a rollback. The credential could then connect again with the access its agent had. Each server now writes the message servers' list over its own copy within a minute of starting, when that list is newer. 2026.2.3 has the same fault. The upgrade to 2026.2.4 isn't such an upgrade, because it signs a new token.
Images
The Weik.io images are on Docker Hub with the exact version as their tag, and no image is tagged latest. images.env pins every image by its digest.
| Image | What it is | Digest |
|---|---|---|
weikio/ | The backend: HTTP API, admin UI, builder and token issuer | sha256: |
weikio/ | The gateway | sha256: |
weikio/ | The agent that runs your integrations | sha256: |
weikio/ | The telemetry forwarder | sha256: |
weikio/ | The log store | sha256: |
weikio/ | The metric store | sha256: |
weikio/ | The trace store | sha256: |
nats: | The message server | sha256: |
traefik: | The TLS terminator | sha256: |
victoriametrics/ | The store program inside weikio/ | sha256: |
otel/ | The OpenTelemetry Collector on your Weik.io servers | sha256: |
victoriametrics/ | The store program inside weikio/ | sha256: |
victoriametrics/ | The store program inside weikio/ | sha256: |
The table shows the start of each digest, and images.env has them in full.
Files
The checksums are from the release's SHA256SUMS files. The Windows CLI and the agent installer are signed by Adafy Oy. curl -fsSL https://weik.io/install.sh | sh checks the CLI before it places it.
| File | What it is | SHA-256 |
|---|---|---|
| weikio-2026.2.4-linux-x64 | The CLI for Linux x64 | 052e0bcb59fbac436945b63f29a0be958051e8b7bcbbc6171fb738a8f7810ac7 |
| weikio-2026.2.4-win-x64.exe | The CLI for Windows x64, signed by Adafy Oy | 4b08af040221622268b214018215325d9c2678cca29ac2528be1c93ae9895909 |
| SHA256SUMS | The checksums of the two CLI files | |
| weikio-agent-win-x64-2026.2.4.msi | The agent installer for Windows Server 2022 and 2025, signed by Adafy Oy | ae6aada69170ed1fa00b0785e1060afb6d116532115c5d1af96d00133355601c |
| SHA256SUMS | The checksum of the agent installer | |
| images.env | Every image of the release with its tag and digest, for the install and upgrade.sh | 8e07d3f5ccfd9fc8ff592af9962a521620d90855b3ec3da95a7c14a5180c9e6a |
| images.lock.json | The same images as JSON | d347048772380b51939b85e1b8e499548c7d61f2f6650bc9bb3faca58a3ccb7c |
| SHA256SUMS | The checksums of images.env and images.lock.json |
The open source projects inside the images, with their versions and licences, are listed in Third-party software.
Upgrade notes
Check these before you upgrade:
- An upgrade from 2026.2.2 or earlier runs the steps of the upgrade to 2026.2.3 first, so the upgrade notes of 2026.2.3 apply to it too.
- The upgrade rewrites the README.md of the single-server and dev stacks and changes nothing a stack runs. Its Backups section describes how a backup collects the copies of the list of withdrawn agent credentials.
- An archive taken before 2026.2.4 has no record of whether its backup collected a copy.
$ sudo sh ./upgrade.sh https://weik.io/downloads/releases/2026.2.4/images.envUpgrades and rollback in the docs has the steps of an upgrade and of a rollback.
Known issues
- The password lock counts per address, so a caller who rotates many addresses avoids it. An account-wide limit is planned for 2026.2.5.
- Under PowerShell's Constrained Language Mode,
install.cmdrefuses a signed installer and says it isn't signed by Adafy Oy. - During an upgrade straight from 2026.2.0 or 2026.2.1, doctor can warn about the delivery notices store. The backend updates the store within a minute, so you don't need to do anything.
- In the admin UI, Delete variable leaves API deployments out of its count. It can then delete a variable that a production API uses, which breaks that API. The CLI lists those API versions.