You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an AUTO_UNLOCK_PASSWORD field which can be provided to automatically start the node on Alby Hub startup. However, this requires Umbrel and Start9 to allow the user to edit this env variable and is not enabled by default, which should be.
How can we improve this for self-hosted hubs?
The text was updated successfully, but these errors were encountered:
Fundamentally, maybe Start9 and Umbrel should not even have unlock passwords. This needs more planning.
I still think this is an issue that we should focus on though e.g. with powercuts or restarts, it's harder for users to get Alby Hub back up and running.
After months of using Alby Hub on Start9 and Umbrel, I’ve rarely needed to enter the unlock password. Once the app is opened, the OS keeps it active, so re-entering the password is only required after a system reboot when I did restart Umbrel, logging in felt natural since all other apps also required re-authentication.
In summary, the unlock password hasn’t been a hassle, it’s only prompted after a reboot, which aligns with expected security behavior. This is based solely on my own experience, and I have not heard complains about this from umbrel or Start9 users so far
There is an
AUTO_UNLOCK_PASSWORD
field which can be provided to automatically start the node on Alby Hub startup. However, this requires Umbrel and Start9 to allow the user to edit this env variable and is not enabled by default, which should be.How can we improve this for self-hosted hubs?
The text was updated successfully, but these errors were encountered: