Installing MineOS on Debian 11

In the wiki, there aren’t instructions for adding webui to Debian 11, only Debian 10. The problematic change between Debian 10 and Debian 11 is the password hashing algorithm. I already answered a question running into a problem with this (Can only login to web UI as root on Debian 11 Bullseye - #3 by BPM), but I thought that I would make it it’s own topic to be easier to find.

Explanation:

The instructions for installing on Debian 10 work, but you aren’t able to log in to the webui. This is because Debian 10 uses sha512 for password hashing and Debian 11 now uses yescrypt. Debian hashes the password using it’s selected hashing algorithm, and stores it in /etc/shadow. When you try to log in to the mineos webui, the webui takes the passed password and hashes it using sha512, then gets the user’s hashed password from /etc/shadow and compares them. If the hashes are the same, the password is correct and the user can log in. There isn’t a problem on Debian 10 because both the webui and the os use sha512 for password hashing. Since Debian 11 is using the yescrypt algorithm and the webui is using sha512, two different hashing algorithms, the password hashes won’t line up, even if you type the correct password.

How to fix:

There are two methods to fix this.

  • Changing the hash method that MineOS uses
  • Changing the hash method that the OS uses

Changing the hash method that the OS uses:

  1. Login as root
  2. Run nano /etc/pam.d/common-password
  3. Scroll to the line that says password [success=1 default=ignore] pam_unix.so obscure yescrypt
  4. Change yescrypt to sha512
  5. Save and exit
  6. Change all of your user passwords using passwd
  7. Restart MineOS daemon

This should fix the problem, allowing you to log in to the mineos webui.

I haven’t found any other differences between using webui on Debian 10 vs 11, but if I find more, I’ll be sure to update this topic.

2 Likes

Thank you for posting this separately because this was my issue

1 Like

Thank you so much for this!

I was about to create a topic because I was encountering this very issue.