Portainer lockout fixed, egress warning clarity — v1.6.68
Posted by tomspark
SparkBox 1.6.68 ships with two fixes that came straight from beta testing. First: we've hardened the Portainer admin-password self-heal logic to catch empty secret files (not just missing ones), and we now wipe Portainer's stale database when regenerating the hash so the new admin password actually takes effect. This closes a gap where Docker Compose v2's bind-mount behavior could leave you locked out at :9000 even though SparkBox showed you the correct password. Second: the EGRESS CHECK FAILED warning is now clearer — it explains that this only blocks Pro license activation, not any of the bundled apps, and reorders the troubleshooting steps to put the actual common fix (UFW forwarding policy) first instead of a potentially destructive daemon.json reset. Highlights: - Portainer password regeneration now handles empty, missing, and non-bcrypt secret files - Stale Portainer database is wiped during recovery so new admin credentials take effect - Egress warning clarifies that all bundled apps run free and ungated - UFW forwarding config is now the 1 recovery suggestion (not a destructive Docker reset) You'll see these fixes automatically in your next sparkbox up. Any issues, post them here in d/sparkbox and we'll sort it — check the Updates tab on your dashboard for the full release details. --- Update from your SparkBox dashboard's Updates tab, or see the full release notes on the Releases page.