I have been running HestiaCP for a while, and it upgrades automatically. However, two days ago I got a hestia message about a backup being full, they I tried to log in with admin and it keeps looping back to the user login page. No relevant errors in the logs, and the auth.log(s) show that admin logs in correctly.
df is not full, so it seems to be a hestia quota error message, or maybe it was full during a upgrade or backup for upgrade.
I tried this:
v-change-user-password admin I get:
cat: /usr/local/hestia/data/users/admin/user.conf: No such file or directory
Now v-change-user-password admin doesnât give an error, but I still canât log in.
Tried:
v-rebuild-all admin restart
cat: /usr/local/hestia/conf/defaults/web.conf: No such file or directory
cat: /usr/local/hestia/conf/defaults/user.conf: No such file or directory
I see a /backup/tmp.IBg6NtRahc/hestia/user.conf so maybe a backup or the upgrade failed half way.
I will try to force the missing files from the source from github, but posting here in case there is a better way. There is probably a hestia command to rebuild the hestia reference files, but I could find it yet and didnât want to risk doing a rebuild all or something because I already semi-locked myself out messing with the firewall as part of my test to try to fix this.
Thank you, I just tried v-change-user-role admin admin but login with admin on port https://...:8083/login Still loops back, no error message about invalid credentials. /var/log/hestia/auth.log says ...successfully logged in
also tried v-change-user-password admin again after and still getting login loop, but backend saying login successful
and logon give no errors in /var/log/hestia/error.log , however:
v-check-user-password admin
gives the following error in /var/log/hestia/error.log
âŚv-check-user-password âadminâ [Error 1]
and I also have following in /var/log/hestia/error.log when I log in to the web control panel, but credential error message onscreen. So it seems to be login in then immediately getting logged out.
For my part, I have never enabled 2FA. I get a successful login in auth.log which is different than âtemposuenderâ. Additionally, all users have the same problem login into the control panel, but the websites and emails are working
I havenât changed anything on the server in months, only the automatic updates run. I see that there have been some files added/updated on May25th, like:
/etc/nginx/conf.d/default.conf.dpkg-dist
and the symlinks to the base domain nginx config have been added/updated today.
My guess is that something changed in nginx and it doesnât match the LocalIP/PublicIP/domain/etc during the login, but I havenât found the log file that tells me exactly what is happening.
I am also getting:
[error] ⌠open() â/usr/local/hestia/web/css/themes/custom/default.cssâ failed (2: No such file or directory), ⌠request: "GET /css/themes/custom/default.cssâŚ
is there a v-update-* that will fix this? It has been a few upgrade iterations that it hasnât touched /usr/local/hestia/conf/hestia.conf and I have already had the hestia version in this file out of sync in the past (eg maybe a year ago or so).