-
-
Notifications
You must be signed in to change notification settings - Fork 675
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HestiaCP Repair Tool #4385
base: main
Are you sure you want to change the base?
HestiaCP Repair Tool #4385
Conversation
Fixes the system in case something isn't working
…tiaCP dir partially done
`-h, --no-dereference affect each symbolic link instead of any referenced file` now script is working normally
the latest commit works, there isn't a reinstall but there is already a permission check and package integrity check. 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 |
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.
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: |
We create the new "hestiaweb" user in 1.9 hestiacp/install/hst-install-debian.sh Lines 1163 to 1168 in 836eaee
|
…php', 'hestia-nginx'
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 |
Regarding this: If you use
So you should modify it to |
I could be wrong but shouldn't it be |
Hestiaweb is not yet available I think, only on version 1.9 |
Just a sec. |
I'll see that later, not on the pc. |
I've corrected the permissions now. |
…e end of the install script part
…he repair script...
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. |
a basic notion can be seen in #4330
what this tool will do?
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