Initially when I setup sparkbox I added a bootstrap token. Since I have updated it keeps asking for a bootstrap token and when I run the sudo sparkbox bootstrap-token it returns nothing.
9 replies
Chris wrote:
Hi noobmaster — this is a known issue that was fixed a couple versions ago. When SparkBox updates, it should remember your bootstrap token from before, but there was a bug where that check didn't work on the update path. The fix shipped in v1.6.157. To get past this: 1. Run sudo sparkbox update (this brings in the fix) 2. Then sudo sparkbox up That should clear the prompt and you'll be back in. If you're already on 1.6.157 or later and still see the prompt after update, let me know the version your box reports and we'll dig into what's happening.
noobmaster wrote:
I am on SparkBox v1.6.694
Chris wrote:
Got it — v1.6.694 has the fix. One quick check: after you run sudo sparkbox update, did you then run sudo sparkbox up? Those two commands together are what applies the fix. If you have already done both and the prompt is still appearing, let me know and we will dig into what is blocking the token recovery.
noobmaster wrote:
It it has the fix then how would run those fix the issue. I have run the commands and it is still an issue
Chris wrote:
Got it — you've done both steps and it's still stuck. Let me dig into this differently. When sudo sparkbox bootstrap-token returns nothing, that usually means one of two things: either the token wasn't preserved in the config file when you updated, or the dashboard thinks you already claimed it but something is out of sync. Let's check which one: 1. Run: grep SBBOOTSTRAPTOKEN /opt/sparkbox/.env If it shows a long alphanumeric string, the token is there. If it shows nothing or SBBOOTSTRAPTOKEN=, then it didn't preserve on update. 2. Also check: sudo sparkbox status — does it show "Dashboard: running"? Send back those two outputs and we'll know exactly what we're fixing.
noobmaster wrote:
dashboard is running grep SBBOOTSTRAPTOKEN /opt/sparkbox/.env returns nothing
Chris wrote:
Got it. The empty token tells us the dashboard was either never claimed or the claim was lost during an update. Let me check one more thing to understand what happened: Run: ls -la /opt/sparkbox/state/ | grep -E "dashboard|session" This will show if the dashboard's session files exist. Then also run: sudo sparkbox logs sb-dashboard | tail -50 Send back those outputs and I can see exactly what the dashboard is reporting.
noobmaster wrote:
A token was claimed when I set this up almost 2 months ago. The commands return nothing
Chris wrote:
Got it — when the commands return nothing, that usually means the directory or files don't exist at all, which is unusual. Let me get a clearer picture. Can you run these in order and paste back exactly what you see (including any error messages): 1. ls -la /opt/sparkbox/state/ — just the first few lines to see if the directory exists 2. ls -la /opt/sparkbox/.env — check if the .env file exists 3. sudo cat /opt/sparkbox/.env | head -20 — first 20 lines (I need to see if there's any SB config at all) If any of those commands say "No such file" or produce errors, that's important info. The fact that the dashboard is running but has no token state or session files is the real clue here. Once I see that, I'll know whether this is a lost config or something else.