Hello Hestia community,
I’m facing an issue when restoring a user but I’m not sure if it’s a bug or miss-configuration from my side. Let me start with some important details
Backup from
Ubuntu 18.04 x64
Hestia VERSION=‘1.0.6’ (might have been updated from a previous release)
Nginx + Apache MultiPHP (–nginx yes --apache yes --phpfpm no --multiphp yes)
Restore to
Ubuntu 18.04 x64
Hestia VERSION=‘1.1.1’ (clean install)
Nginx + Apache MultiPHP (–nginx yes --apache yes --phpfpm no --multiphp yes)
The issue
When running v-restore-user
I get these errors:
-- USER --
2020-05-02 16:43:12 [USERNAME]
-- WEB --
2020-05-02 16:43:13 [FQDN]
tee: /home/[USERNAME]/web/[FQDN]/stats/.htaccess: Permission denied
AuthUserFile /home/[USERNAME]/web/[FQDN]/stats/.htpasswd
tee: /home/[USERNAME]/web/[FQDN]/stats/.htaccess: Permission denied
AuthName "Web Statistics"
tee: /home/[USERNAME]/web/[FQDN]/stats/.htaccess: Permission denied
AuthType Basic
tee: /home/[USERNAME]/web/[FQDN]/stats/.htaccess: Permission denied
Require valid-user
tee: /home/[USERNAME]/web/[FQDN]/stats/.htpasswd: Permission denied
[STATS_USER]:[STATS_CRYPT].
-- DNS --
2020-05-02 16:43:20 [FQDN]
-- MAIL --
-- DB --
2020-05-02 16:43:20 [DB]
-- CRON --
2020-05-02 16:43:21 0 cron jobs
-- USER FILES --
2020-05-02 16:43:21 .bashrc
2020-05-02 16:43:22 .profile
2020-05-02 16:43:22 .bash_logout
The restored WordPress site (files + DB) seems to be working OK. I also checked the DNS entries and they seem fine. Awstats seem OK too.
It looks as though these issues appear only if the user does not exist on the destination server.
- When I run another
v-restore-user
(right after the 1st restore) using exactly the same backup file, I get no such issues. - If I delete the user completely on the destination server and run
v-restore-user
again from the same backup file, I have the same issues again. - If I run the restore once more, I get no issues.
One thing to note… Although the backup file was created by Hestia, it might be possible that this user has been restored from a Vesta installation (i.e. Vesta > Hestia 1.0.6 > Hestia 1.1.1). I don’t know if that’s related though.
If you think this could be a bug, please tell me and I’ll raise an issue on github.