A small fix release. spinuptui ssh-exec stops refusing a harmless WP-CLI read, and a failed Uptime Kuma connection now tells you why it failed.
Fixed
- A quoted
wpcommand that ends in a flag is allowed.spinuptui ssh-exec <site> -- bash -c 'wp --info'was denied because the closing quote landed on the flag and the guard read it as an option missing its value. - Uptime Kuma connection errors show the actual reason. With a long instance URL, the cause (a TLS, DNS or proxy problem, say) ran past the edge of the connect form, leaving only
Couldn't reach Uptime Kuma at https://…:. The error lines in the connect form and the Alerts panel now wrap. If you couldn't connect before, update and try again: the message should now say what went wrong.