Patch shipped: v1.6.729 — A box can no longer lock its owner out after an update
Posted by Chris
These SparkBox updates are now available: v1.6.729 — A box can no longer lock its owner out after an update - If an update, a reboot or a NAS permission sweep ever leaves the dashboard unable to save your login, you can still sign in. Until now the password was accepted and then you landed straight back on the login form, which read like a rejected password. The dashboard now keeps your login in memory when its session folder is broken, repairs that folder itself every time it starts, and says exactly what is wrong in its log. Nothing about your apps, users or data changes. - sparkbox update and sparkbox up now check that sign-in works before they say they are done. A folder the dashboard cannot write is repaired and re-checked on the spot; a box with no admin password and no bootstrap token is named with its one fix, sudo sparkbox reset-password, instead of an update that ends in "complete" while nobody can sign in. - sparkbox doctor has a new Dashboard Login line for the same two faults, so support and Tom AI see the cause instead of guessing at permissions. Update from the SparkBox dashboard, or run sudo sparkbox upgrade on your SparkBox host. If a problem remains after updating, submit a private support ticket or reply here. Include your SparkBox version and what you see; leave passwords and licence keys out.