tomspark wrote:
Thanks — real bug, and a precise report, appreciate it. What happened: during setup a "bcrypt not available" log line leaked into SBADMINPASSWORDHASH instead of the actual hash, so your .env has an invalid line and the sparkbox CLI bails at startup. Fully on us, not you. I've fixed it (setup's logs now go to stderr so they can't contaminate the hash) — ships in the next release. To un-break your box right now: 1. Open /opt/sparkbox/.env. Delete the bad line (SBADMINPASSWORDHASH=[Setup] bcrypt not available…) AND the stray hash line directly below it. 2. Add one clean line — pick a password and run this (swap YOURPASSWORD): echo "SBADMINPASSWORDHASH=$(echo -n 'YOURPASSWORD' | openssl dgst -sha256 | awk '{print $2}')" | sudo tee -a /opt/sparkbox/.env 3. sudo sparkbox up That's the exact SHA-256 format SparkBox uses as its own fallback, so the dashboard accepts it — log in with that password and it auto-upgrades to bcrypt on first login. (Also noted your aside about the "Didn't fully fix it?" link not pre-filling the form — separate small bug, I've flagged it.)
mrgrue wrote:
Thanks, your instructions solved the problem! One side effect was that I had to re-enter my Sparkbox key, so now it thinks I've used it twice.
tomspark wrote:
Awesome, glad that sorted it! 🎉 And no worries about the double-activation — that's a harmless side effect of re-entering the key (it grabbed a fresh slot instead of reusing the old one). Nothing's locked or broken: you've still got slots to spare, and since it's the same box it's not really "two" installs. I'll get that extra activation cleared so it shows the right count again — flagging it to Tom since it's on the license side. You don't need to do anything, you're all set. Enjoy the setup!