Can't login panel after update

1

After updating hestiacp, I cannot login the panel.

It says : Unsupported hash method

image
image705×530 33.5 KB

2

v-change-user-password username newpassword

And try it again

3

I did. still not working.

I have checked even with v-check-user-password USER PASSWORD and it matches.

4

root@server:/usr/local/hestia/bin# tail -f /var/log/auth.log

Feb 17 14:50:02 server CRON[2591199]: pam_unix(cron:session): session closed for user admin
Feb 17 14:52:01 server CRON[2591643]: pam_unix(cron:session): session opened for user admin(uid=1001) by (uid=0)
Feb 17 14:52:01 server sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1001)
Feb 17 14:52:01 server sudo: pam_unix(sudo:session): session closed for user root
Feb 17 14:52:01 server CRON[2591643]: pam_unix(cron:session): session closed for user admin
Feb 17 14:52:44 server nologin: Attempted login by root (UID: 0) on /dev/pts/0
Feb 17 14:54:01 server CRON[2591683]: pam_unix(cron:session): session opened for user admin(uid=1001) by (uid=0)
Feb 17 14:54:01 server sudo: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1001)
Feb 17 14:54:01 server sudo: pam_unix(sudo:session): session closed for user root
Feb 17 14:54:01 server CRON[2591683]: pam_unix(cron:session): session closed for user admin

root@server:/usr/local/hestia/bin# tail -f /var/log/hestia/auth.log

2025-02-17 14:45:29 admin 127.0.0.1 successfully logged in
2025-02-17 14:45:32 admin 127.0.0.1 failed to login
2025-02-17 14:45:36 admin 127.0.0.1 successfully logged in
2025-02-17 14:45:41 admin 127.0.0.1 successfully logged in
5

root@server:/usr/local/hestia/bin# v-get-user-salt admin IP json
{
“admin”: {
“METHOD”: “sha-512”,
“SALT”: “r3LlLQXHRH6NwUPq”,
“TIME”: “15:11:37”,
“DATE”: “2025-02-17”
}
}

6

I wanted to check code,

I edited PHP

file_put_contents(“output.txt”, “Return Code: " . $return_var . “\n” . implode(”\n", $output));

and checked the error code and it says


Return Code: 1
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required

then I checked the permission of directory

root@server:~# ls -l /usr/local/hestia/bin/
total 2296
-rwxr-xr-x 1 hestiaweb hestiaweb  2268 Aug 26 08:31 v-acknowledge-user-notification
-rwxr-xr-x 1 hestiaweb hestiaweb  3454 Aug 26 08:31 v-add-access-key
-rwxr-xr-x 1 hestiaweb hestiaweb  9734 Aug 26 08:31 v-add-backup-host
-rwxr-xr-x 1 hestiaweb hestiaweb  2759 Aug 26 08:31 v-add-cron-hestia-autoupdate
-rwxr-xr-x 1 hestiaweb hestiaweb  2760 Aug 26 08:31 v-add-cron-job
-rwxr-xr-x 1 hestiaweb hestiaweb  1522 Aug 26 08:31 v-add-cron-letsencrypt-job
-rwxr-xr-x 1 hestiaweb hestiaweb  1779 Aug 26 08:31 v-add-cron-reports
-rwxr-xr-x 1 hestiaweb hestiaweb  1482 Aug 26 08:31 v-add-cron-restart-job

the user is hestiaweb, is that correct ?

7

Check /etc/sudoers.d/hestiaweb

8

Ok I fixed, thanks

  525  cat /etc/sudoers.d/hestiaweb
  526  sudo passwd -u hestiaweb\
  527  sudo passwd -u hestiaweb
  528  sudo passwd -u hestiaweb -p
  529  getent passwd hestiaweb
  530  sudo passwd -S hestiaweb
  531  sudo passwd hestiaweb
  532  sudo usermod -s /usr/sbin/nologin hestiaweb
  536  sudo visudo -f /etc/sudoers.d/hestiaweb
  537  sudo systemctl restart hestia
  538  sudo systemctl restart nginx
  540  tail -n20 /var/log/hestia/error.log
  541  sudo -l -U hestiaweb
  542  sudo usermod -aG shadow hestiaweb
  543  sudo chown root:shadow /etc/shadow
  544  sudo chmod 640 /etc/shadow
  545  sudo touch /usr/local/hestia/log/auth.log
  546  sudo systemctl restart hestia
  547  sudo systemctl restart nginx
9

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.