Skip to content

v0.9.58-alpha — Console reliability behind SSO + gateway-safe brute-force protection

Choose a tag to compare

View all tags
@takwerx takwerx released this 15 Jun 07:08
v0.9.58-alpha
34df2ee

Console reliability behind SSO + gateway-safe brute-force protection

The console dashboard stays usable on single-sign-on deployments, and brute-force protection can no longer accidentally lock out your own gateway.

Highlights

  • Dashboard works behind SSO. On deployments where the console sits behind single sign-on, the dashboard's background calls — the "Check for new release" and "What's using CPU/RAM" buttons and the live CPU/RAM/disk gauges — could fail once your login session lapsed. The page still looked logged in, but those controls quietly errored until you reloaded. The console now handles an expired session cleanly, so the buttons and gauges keep working as expected.
  • Gateway-safe brute-force protection. fail2ban gains a trusted-upstream whitelist. On a box behind a reverse proxy, load balancer, or cloud gateway, the upstream's address is never banned — preventing a self-inflicted outage where a single traffic blip could otherwise block every site at once. Localhost and the box's own private network are always trusted; additional gateway/proxy networks can be added from the Fail2ban page.
  • Console stays responsive on a plain restart. The console's web server now picks up its full thread count on any restart (not only via Update Now), so busy single-worker consoles stay snappy.

Upgrade: applied automatically on the next console update. No manual steps.

Assets 2
Loading