Changelog

v0.21.1

Uptime Kuma connection reliability fix · July 10, 2026

A small reliability release: fixes an Uptime Kuma connection failure some users could hit depending on their network path to their Kuma instance.

Fixed

  • Connection now falls back to HTTP long-polling. SpinupTUI talks to Uptime Kuma over its socket.io management API, and the client previously connected over WebSocket only. If a reverse proxy or CDN sits in front of your Kuma instance and doesn't forward the WebSocket upgrade headers, that made the connection fail outright with no way to recover. It now also tries HTTP long-polling, so a proxy that mishandles the WebSocket upgrade no longer blocks the connection entirely.
  • Connection failures no longer swallow the real reason. A failed connect could previously show up as Couldn't reach Uptime Kuma at https://…: with nothing after the colon — the underlying error's message came back empty, and that empty string got used as-is. The error now checks the underlying error's description and error code before giving up, so a connection failure actually tells you something useful instead of a dangling colon.

Notes

  • If you were hitting a connection error before this release, it's worth retrying — the polling fallback may resolve it outright. If it still fails, the error message should now be more informative about why.

View on GitHub →