I’m having a problem with HestiaCP after an upgrade.
The login page loads fine, my credentials are accepted, and the auth log shows successful login, but the panel immediately redirects me back to /login/ instead of opening the dashboard. This happens with multiple accounts, different browsers, incognito mode, the hostname, and also the server IP directly.
What I already checked:
• Hestia, nginx, and apache are running
• panel on port 8083 is reachable
• server reboot did not help
• restarting services did not help
• disabling IP session check temporarily did not help
• changed password of cp admin user
• removed old session files
• changed permissions
In /usr/local/hestia/log/auth.log, logins are marked as successful.
In /var/log/hestia/nginx-error.log, I repeatedly see requests for:
• /css/themes/custom/.css
The issue seems similar to the login-loop reports after Hestia 1.9.x upgrades, and my server is now on 1.9.4.
Has anyone seen this exact behaviour and found the proper fix?
Double check that the errors you see in that log are from today. There is a bug rotating those logs and possibly the current log is nginx-error.log.1 instead of nginx-error.log
If you don’t see any error, backup dir /usr/local/hestia/ and reinstall the package (it won’t remove/change/etc. any user)
After checking the logs more closely, the real problem turned out to be a malformed setting in /usr/local/hestia/conf/hestia.conf: FILE_MANAGER=“true” was set with the wrong quoting, while it should have been FILE_MANAGER=‘true’.
Because of that, v-list-sys-config json returned malformed JSON for the FILE_MANAGER field, which broke Hestia’s internal config/session loading after login.
I corrected the line, restarted Hestia, and after that the login worked normally again.
For future troubleshooters, make sure v-list-sys-config returns a healthy JSON output.