When Zaparoo Core fails to start, it now stays up in a failed state and explains itself: /health and / carry the reason (ZaparooProject/zaparoo-core#1526, ZaparooProject/zaparoo-core#1527). zaparoo-cli doctor never asks for it.
Seen on Windows with Core in that failed state, zaparoo-cli --device … doctor reports only:
"websocket-version", ok:false, "WebSocket upgrade rejected with HTTP 503"
remediation: ["Check host, port, Core service state, firewall, and SSH artifact fallback."]
The explanation is sitting one request away, and the generic advice points at the network when the network is fine.
Ask: when the WebSocket upgrade is refused with 503, fetch /health and show Core's own failure reason in place of the generic remediation. Keep the current advice for any other failure.
The point of Core's failed-startup state is that a stuck install can say what's wrong, and doctor is the first tool anyone reaches for.
When Zaparoo Core fails to start, it now stays up in a failed state and explains itself:
/healthand/carry the reason (ZaparooProject/zaparoo-core#1526, ZaparooProject/zaparoo-core#1527).zaparoo-cli doctornever asks for it.Seen on Windows with Core in that failed state,
zaparoo-cli --device … doctorreports only:The explanation is sitting one request away, and the generic advice points at the network when the network is fine.
Ask: when the WebSocket upgrade is refused with 503, fetch
/healthand show Core's own failure reason in place of the generic remediation. Keep the current advice for any other failure.The point of Core's failed-startup state is that a stuck install can say what's wrong, and
doctoris the first tool anyone reaches for.