Good Day Sir, I followed the steps above and still cannot access the sites and the admin panel. everything is Active(running) [ Hesita.service, nginx, apache2 ]
my panel got updated to 1.9.2. Thank you
I had same issue. Seems the new hestiaweb user wasn’t created properly during the upgrade. I had to create that user manually, and then fix permissions and ownership on a whole bunch of folders/files.
Make sure the sessions folder has the permissions and user shown in the screenshot. Located at /usr/local/hestia/data/ (see screenshot.)
I also had to make sure the logs and tmp folder had the following permissions and user assigned - located in the /usr/local/hestia/web/fm/private folder (see screenshot for permissions)
Next make sure the hestiaweb file within /etc/sudoers.d includes the following info (see screenshot). I modified it via vi hestiaweb command.
Add the following to it:
sudo is limited to hestia scripts
hestiaweb ALL=NOPASSWD:/usr/local/hestia/bin/*
Screesnshot below is the contents of my hestiaweb located there after running vi editor. Change to what you see if yours is different. Make backup of things obviously before making changes.
Contents of my hestiaweb file located at /etc/sudoers.d:
This is the major things I had to resolve to fix my issues, including access to the Hestia Control Panel. To be frank, tons of stuff broke on mine and I am lucky I was able to figure it out with the help of ChatGPT and referencing my other server also running HestiaCP. If I didn’t have the other server which received a smooth upgrade, I don’t think I’d have figured out how to fix this.
Good luck!
P.S. I did a bunch of other stuff too, so if this doesn’t fix your issue, let me know and I can reference my ChatGPT troubleshooting chat. But yeah, the above was the main issues.
1 Like
I’ve just created an account on this forum to say:
thank you, this worked for me!
1 Like
All of the above said things are being already set but still i can’t access the filemanager from admin user, but can access with other users. What may be the problem?
Fixed by changing the user admin ssh access to bash in UI. User>admin>advanced option>SSH access>bash.
1 Like