19 replies
Chris wrote:
Hi m2elite — that blank white page is a known issue that shipped fixed in v1.6.71. The dashboard was compressing pages and closing the connection early, leaving your browser with an incomplete page. To fix it, open your dashboard, go to Settings Updates, and click Update to bring it to the latest version. After it finishes, refresh your browser. The new version no longer compresses the dashboard pages, so they always arrive whole. Let me know if you hit any issues during the update.
m2elite wrote:
cannot update
Chris wrote:
Hi m2elite -- let me help figure out what is blocking the update. First, a quick check: open your dashboard and go to Settings System to see your current version. Can you reply with: 1. Your current version number (v1.6.something) 2. What happens when you click the Update button - error message, spinner, or nothing? If the button is not responding, try a hard refresh (Ctrl+F5) and try again. Once I see those details, I can help with the next step.
m2elite wrote:
v1.6.701. Just refreshes and states it cannot check for updates try hard reset
Chris wrote:
m2elite — thanks for that detail. You're on v1.6.701 already, so that part is current. The "cannot check for updates" message means the dashboard can't reach the update service right now, not that an update is waiting. Let's check if it's a network issue or just browser cache. Try these two steps: 1. Hard refresh the dashboard (Ctrl+Shift+R on Windows, Cmd+Shift+R on Mac) to clear your browser's cached dashboard code. 2. Restart the dashboard container by opening a terminal and running this command: sudo sparkbox restart dashboard After the restart, refresh the browser and check Settings System again. If the Update button still says "cannot check for updates," that's a network issue on your box — the dashboard can't reach the update service. Reply with: 1. Did the restart fix it? 2. Are you using any VPN or custom network settings that might block updates? Let me know what you find.
m2elite wrote:
try that i am not using a VPN or firewall setup
Chris wrote:
m2elite — let me know once you've run those two steps (the hard refresh and the sudo sparkbox restart dashboard), and let me know what happens: 1. Did the Update button change or show any different message? 2. Can you now reach the Settings System page without the blank white page? Once the restart is done, wait about 30 seconds for the dashboard container to fully come back up, then try refreshing your browser. Reply with what you see.
m2elite wrote:
still no luck now iit will not accept my password
Chris wrote:
I’m sorry — I sent you through a password reset and a manual session-directory change without proving either was the cause. Your earlier version was v1.6.701; the dashboard-session fix is in v1.6.708, and the update button was not reaching the update service. From the WSL host, run this one command: sudo sparkbox upgrade That moves SparkBox itself to the current release while keeping your settings and data. When it finishes, reply with the version it prints; please do not reset the password again yet. I’ve corrected this guidance so the unsupported directory explanation is not repeated to the next person.
m2elite wrote:
did that will not past thelogin splash page it accepts the password and i see a csannot load service smessage
m2elite wrote:
Internal Server Error on the webpage
Chris wrote:
I’m sorry this is still failing after the upgrade. The current symptom is a dashboard server error, not evidence that your password is wrong. From the WSL terminal, run this one read-only check: sudo sparkbox logs dashboard | tail -20 Please paste only those last 20 lines, after removing any private values if they appear. I’ll use the actual dashboard error to choose the next step rather than repeat another reset or directory change. I’ve corrected this guidance so we do not keep sending people through unsupported password or folder changes.
m2elite wrote:
Error: EACCES: permission denied, open '/app/state/sessions/bpuFWEbzcdVNZKhYrLjDB8eFNJPFUSVO.json.tmp.1.fdf3d216' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/7C6DpByLOEF6M1LZvG7WC5sVISQvktA.json.tmp.1.99daa85e' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/DLGpAcPN4uNQ3WfxHMupWnic6rbaKH.json.tmp.1.eecfcb82' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/aVsmqnH7w0uATSXHTegvYilCjmpOOVJ.json.tmp.1.e98a4cef' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/bwzVWsj0iwLJEQ7Ln1XLKsyZCEuxgbnw.json.tmp.1.d78135b9' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/TeqoTrjGMYcOQ76gX-i5QhVSY2pL7bL.json.tmp.1.bfa34e61' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/4-ksxcOgbbQVZGzpIls9FINqRludoN.json.tmp.1.d0d366b7' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/jBP18JvNBbX1OgzvE8U2tZO34Cs6dn9w.json.tmp.1.9ae3b2b0' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/CzyTDLuGfCcQcvw2AslkVpWgN5T4dxoZ.json.tmp.1.bb79c5ab' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/COj3MzsyErnNmJBJYkAM2CziX8c6M6D.json.tmp.1.4ac8fc41' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/uPS4CwzBC6D-ijN4HNik8VYAU9uRdmc5.json.tmp.1.bd51249f' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/XVpMHTpQw2Kxh0KTZ2AByTANDKBlCeSf.json.tmp.1.e2a41ee3' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/7MhWCpt8sz04l1-nPq0sbd47nYThMqJ.json.tmp.1.dee0e898' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/m-LWP7UH2EDLrUddh6th61wxgkANkpQO.json.tmp.1.6b64771e' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/xysxI2IGCgswPSAuu-SR2PSAUoQ10DXh.json.tmp.1.0f6ca354' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/V6A6CmMVomnBrZKRKJfG-KRmhpxHc0x.json.tmp.1.a60a44bc' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/C11OdkVYsGbXO5q2QUKbklxb5FTFPeQQ.json.tmp.1.e09f1239' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18) Error: EACCES: permission denied, open '/app/state/sessions/IMxsN8Vt7sEeSp1x5dtAjDa830hQdg.json.tmp.1.b51c20b6' at async Object.open (node:internal/fs/promises:637:25) at async writeFileAtomic (/app/lib/atomic-write.js:133:18)
Chris wrote:
m2elite — I’m sorry. The log confirms the dashboard cannot write its session files (EACCES), so this is not a bad password. My earlier advice to create and chown a different directory was wrong and did not address the path SparkBox is using. The current release (v1.6.709) repairs this session folder during the password-reset path. From the WSL terminal, run: sudo sparkbox upgrade sudo sparkbox up Then try the password again. Please do not reset it or change folder ownership manually again. I’ve corrected this guidance so the unsupported directory fix is not repeated to the next person.
Chris wrote:
I’m sorry — the upgrade and sparkbox up did not fix the session-folder error you pasted. That error means the dashboard accepts the password but cannot save the browser session because the session folder is not writable. In v1.6.709, the password-reset command repairs that folder before restarting the dashboard. From the WSL terminal, run this once: sudo sparkbox reset-password Complete its interactive prompts, then sign in with the new password it accepts. Please do not manually create or chown another directory. I’ve corrected this guidance so the unsupported folder workaround is not repeated to the next person.
m2elite wrote:
ok i am finally in
m2elite wrote:
i was in but nowcannot no longer logon will have to uninstall i was only using it for the jellyfin media setup
Chris wrote:
I’m sorry this is still failing, and I’m sorry the earlier replies kept sending you through resets and unsupported folder ownership changes. Your logs showed a session-write permission error, but the latest check showed both /opt/sparkbox/state and state/sessions as 0:10, so we do not have evidence that another ownership change would help. Please do not uninstall yet. From the WSL terminal, run this one read-only check: sudo sparkbox logs sb-dashboard | tail -20 and paste only those lines after removing private values. I’ve corrected the guidance so we do not repeat the blanket chown or another password reset.