HestiaCP Repair Tool

[tlcd96]

a basic notion can be seen in #4330

what this tool will do?

• Correct HestiaCP dir permissions
• Integrity check HestiaCP
• Reinstall Broken Hestia Packages
  • hestia
  • hestia-nginx
  • hestia-php
• Correct plugins and integrations
• Reinstalls of packages that might be broken
• Fancy UI in Bash for all the steps

Fixes the system in case something isn't working

Instead of searching for a fix, this will do an integrity check and permission check on the file system

[tlcd96]

the latest commit works, there isn't a reinstall but there is already a permission check and package integrity check.
it's missing the integrations, plugins and reinstalls in case of a integrity failure. this is not made yet for Hestia packages due to testing. the next commit, there will be a

	echo "reinstall needed: 'hestia'"
	.......
	$(apt update)
	$(apt install --reinstall hestia -y)
	.......
	echo "reinstall needed: 'hestia-php'"
	.......
	$(apt update)
	$(apt install --reinstall hestia-php -y)
	.......

so on and so forth...

[jaapmarcus]

the latest commit works, there isn't a reinstall but there is already a permission check and package integrity check. it's missing the integrations, plugins and reinstalls in case of a integrity failure. this is not made yet for Hestia packages due to testing. the next commit, there will be a

	echo "reinstall needed: 'hestia'"
	.......
	$(apt update)
	$(apt install --reinstall hestia -y)
	.......
	echo "reinstall needed: 'hestia-php'"
	.......
	$(apt update)
	$(apt install --reinstall hestia-php -y)
	.......

so on and so forth...

No it will not check the permissions with a new install from 1.9.0 as base ...

admin:admin will get changed

[tlcd96]

No it will not check the permissions with a new install from 1.9.0 as base ...

admin:admin will get changed

if admin:admin will be changed, there is, on the script, the chown permissions to change. it can be changed to whatever we need

I can add a parameter to bypass the check of the permissions of the HestiaCP directory. But I don't think that is needed, cause this script is to bypass most of the troubleshooting.

• if there is a fix on this script, apply it.

now if there isn't, we report to the user, on the script, that the issue is more complicated and that this repair tool cannot fix.

how to do that? simple, checking if there was a change on a global variable on the script, for example: any_fix_done="0"
if that is equal to "0" we report that we couldn't find any problem and if any problem persists, to contact on the forum.

[jaapmarcus]

No it will not check the permissions with a new install from 1.9.0 as base ...
admin:admin will get changed

if admin:admin will be changed, there is, on the script, the chown permissions to change. it can be changed to whatever we need

I can add a parameter to bypass the check of the permissions of the HestiaCP directory. But I don't think that is needed, cause this script is to bypass most of the troubleshooting.

• if there is a fix on this script, apply it.

now if there isn't, we report to the user, on the script, that the issue is more complicated and that this repair tool cannot fix.

how to do that? simple, checking if there was a change on a global variable on the script, for example: any_fix_done="0" if that is equal to "0" we report that we couldn't find any problem and if any problem persists, to contact on the forum.

We create the new "hestiaweb" user in 1.9

hestiacp/install/hst-install-debian.sh

Lines 1163 to 1168 in 836eaee

	# Generate a random password
	random_password=$(gen_pass '32')
	# Create the new hestiaweb user
	/usr/sbin/useradd "hestiaweb" -c "$email" --no-create-home
	# do not allow login into hestiaweb user
	echo hestiaweb:$random_password | sudo chpasswd -e

[johnnyq]

Nice script so far and is much needed, just a suggestion but how about cleaning up old backups especially for backups of users that don't exist anymore and remove all php sessions etc

[sahsanu]

@tlcd96

Regarding this:
check_ownership "/usr/share/phpmyadmin/tmp" "root:hestiamail" "1"

If you use root:hestiamail as owner:group you will see this warning in phpMyAdmin

Warning The $cfg['TempDir'] (/usr/share/phpmyadmin/tmp/) is not accessible. phpMyAdmin is not able
to cache templates and will be slow because of this. 

So you should modify it to hestiamail:www-data or hestiamail:hestiamail

[johnnyq]

@tlcd96

Regarding this: check_ownership "/usr/share/phpmyadmin/tmp" "root:hestiamail" "1"

If you use root:hestiamail as owner:group you will see this warning in phpMyAdmin

Warning The $cfg['TempDir'] (/usr/share/phpmyadmin/tmp/) is not accessible. phpMyAdmin is not able
to cache templates and will be slow because of this. 

So you should modify it to hestiamail:www-data or hestiamail:hestiamail

I could be wrong but shouldn't it be hestiaweb:www-data

[tlcd96]

Hestiaweb is not yet available I think, only on version 1.9

[tlcd96]

Just a sec.

[tlcd96]

I'll see that later, not on the pc.

[tlcd96]

@tlcd96

Regarding this: check_ownership "/usr/share/phpmyadmin/tmp" "root:hestiamail" "1"

If you use root:hestiamail as owner:group you will see this warning in phpMyAdmin

Warning The $cfg['TempDir'] (/usr/share/phpmyadmin/tmp/) is not accessible. phpMyAdmin is not able
to cache templates and will be slow because of this. 

So you should modify it to hestiamail:www-data or hestiamail:hestiamail

I could be wrong but shouldn't it be hestiaweb:www-data

I've corrected the permissions now.

[tlcd96]

@tlcd96

Regarding this: check_ownership "/usr/share/phpmyadmin/tmp" "root:hestiamail" "1"

If you use root:hestiamail as owner:group you will see this warning in phpMyAdmin

Warning The $cfg['TempDir'] (/usr/share/phpmyadmin/tmp/) is not accessible. phpMyAdmin is not able
to cache templates and will be slow because of this. 

So you should modify it to hestiamail:www-data or hestiamail:hestiamail

I could be wrong but shouldn't it be hestiaweb:www-data

As per hestia, 1.9, the web user will be changed to hestiaweb with group hestiaweb. That's why the permissions where changed again. Please do not use alpha/beta code without having sure it won't mess with your installation.