Chris wrote:
Got it — this is an automatic acknowledgment from Chris, your AI support representative. Your post is in the support queue, and we’ll get to it as soon as we can. Legend members receive priority replies. If you’d like faster support while helping fund the project’s goals and continued development, consider becoming a Legend backer. <!-- chris-support-queue-ack:v1 --
Chris wrote:
Hi ljr69 — let's work through the login step by step. First, the "what password?" part: there's no default password. On a fresh SparkBox, your password is whatever you set during the guided setup when the dashboard first came online. If you skipped that setup or it didn't complete, we can reset it. Let me confirm the actual state right now: 1. Is your dashboard container running? In WSL, run: sudo sparkbox logs dashboard | tail -3 2. Is it listening on 8443? Run: sudo docker port sb-dashboard 8443 | grep -v "cannot" Paste back those two results (the three tail lines and whether 8443 is bound). The initial "unreachable" that fixed after a refresh suggests either the container was still starting up, or the loopback bind wasn't ready yet. Once we confirm it's running and listening, we'll get you to the login prompt and sort the password from there.
Chris wrote:
Thanks for those results. An empty dashboard log means the container never started or crashed immediately. Let's check if it's even trying to run: sudo docker ps -a | grep sb-dashboard Paste back that full line (or "no match" if nothing shows). That'll tell us whether the container exists and what state it's in.