Vesta Control Panel - Forum

Follow these steps, it solved it for me under Debian:
viewtopic.php?t=9724

skurudo wrote:[This is news to me, you know how to use scp or rsync? What error do you get and what command use?

I connect to it with FTP client, using SFTP/SSH connection.
Probally not the best of solution but it used to work fine.
The proposed solutions should work better?

I have no idea what is causing it, running Debian 8 here and it showed up after it made a backup via the cron. Deleted the backup I had and it shows backups 0 but still it displays /backup that can't be deleted. http://i66.tinypic.com/zv7hmq.png This file is empty: /usr/local/vesta/data/users/admin/...

When running the command v-list-user-backups is retuns: BACKUP TYPE SIZE RUNTIME TIME DATE ------ ------ ------ ------ ------ ------ /backup NULL NULL NULL 10:57:12 2015-12-07 admin.2015-12-07.tar local 15 1 05:10:04 2015-12-07 Also in admin is display /backup entry. How to fix that?

I have noticed that uploading files using SSH is very unreliable, it usually fails.
Debian 7 or 8 makes no difference.
It was not so the case with previous VestaCP version.
What could be the cause?

I have the same issue. Running VestaCP Version 0.9.8 (i386) Release 15 on Debian 8 32 bit. Error messages in phpmyadmin are: The phpMyAdmin configuration storage is not completely configured, some extended features have been deactivated. Connection for controluser as defined in your configuration f...

When manually running cron it returns: executing /etc/cron.daily/quotacheck /etc/cron.daily/quotacheck: run-parts: failed to exec /etc/cron.daily/quotacheck: Exec format error run-parts: /etc/cron.daily/quotacheck exited with return code 1 Adding t#!/bin/sh to /etc/cron.daily/quotacheck solved this ...

Probally not a VestaCP specific question, but how can I re-create a manually deleted error.log file in my web directory?
Vesta doesn't seem to create a new one by itself?

I realise this is a old topic.
Anyway, I have the same problem on Debian 7 and have not been able to find a working solution.

Will this issue be fixed in the next VestaCP update?

Having the same issue as topic poster.
Its a fresh install on a VPS running Debian Wheezy.

Is there a solution for this?