Release LoadGen Api, Appliance and MCP Server: 1.0.0.11967
LoadGen General
- No general changes in this release.
LoadGen Api
- [#8926] Deleting a managed PowerShell script under Uptime Monitoring → Scripts that is still in use now tells you exactly which uptime check(s) reference it, instead of only the generic "Checks that reference this script must be detached first…" message. The API now exposes which uptime checks reference a script, allowing the delete-confirmation dialog to name the blocking check(s) up front.
- [#8966] Fixed federated SSO logout failing with the identity provider's "Bad Request — The request is otherwise malformed" error page (observed with Authentik), even when a Logout URL was explicitly configured. The API previously derived the post-logout return address from an internal address that the identity provider rejected; it now uses the browser-facing return address supplied by the frontend, validated before use, and when no address is supplied (older frontend builds) the previous behavior is kept, so mixed-version setups keep working. Note that your identity provider may also need
https:///loginregistered as an allowed redirect URI for the end-to-end flow to succeed.
LoadGen Appliance
- Reliable first reboot after an appliance update. Fixed the appliance's Docker stack half-starting on the first reboot after an image update: only the reverse proxy and certificate services came up, the WebGUI was unreachable, and a second reboot was always needed. Containers left over from the previous version collided with the new stack at boot (a "container name already in use" conflict aborted startup midway). The boot-time startup is now self-reconciling: if the normal start fails, the stack is torn down cleanly (including leftover containers) and brought up from scratch. Fresh appliance images ship with the fix, and existing appliances self-heal automatically on the next agent restart.
LoadGen MCP Server
- No MCP Server changes in this release.