Vesta Control Panel - Forum

UPDATE: skurudo, you were right. v-rebuild-user DID need to be run after all of this but there was another problem, that could possibly be OS related not VestaCP related. After the restore, the permissions were incorrect. I had to chown root:user * in the /home/user/conf/web/ folder in order for res...

There is no way to verbose output. However nearly everything that can go wrong that ends the process stores errors in one of these places: /var/log/vesta/system.log /var/log/vesta/backup.log /var/log/vesta/auth.log /var/log/vesta/nginx-error.log /usr/local/vesta/php/var/log/php-fpm.log When your res...

Replicated, rebuilt user, it doesn't remove the errorous include. Probably because the scripts for the restore already rebuild the user since the user name and other info could be different in the backup. The problem is solved on my end just pointing it out for others that might get similar errors. ...

Still collecting more info so I can dump it here, but here's a possible bug I discovered. WHen restoring a backup to a different server with a different username than source username, everything went fine, except for some reason /etc/nginx/conf.d/vesta.conf automatically loaded an httpd.conf as well...

Yes I have followed all of those instructions. It suggests creating the folder and then chowning it. That made no difference. I've searched google quite a lot for this one.

If I also create the clamd.sock file INSIDE that folder, it says connection refused.

I get this error every time an inbound emails comes in: 2016-03-27 21:56:59 1akIg7-0005rW-JK malware acl condition: clamd: unable to connect to UNIX socket (/var/run/clamav/clamd.sock): No such file or directory 2016-03-27 21:56:59 1akIg7-0005rW-JK H=mail-wm0-f51.google.com [74.125.82.51] X=TLSv1.2:...