Article ID: 124254, created on Jan 22, 2015, last review on Jan 22, 2015

  • Applies to:
  • Plesk 12.0 for Linux
  • Plesk 11.5 for Linux
  • Plesk 12.0 for Windows
  • Plesk 11.5 for Windows


Cannot create backups in FTP repository, backups are stored in server repository.

In log files there are errors like:

# less /usr/local/psa/PMM/logs/backup-2013-11-29-00-54-02-643/backup.log
[2013-11-29 01:19:42.861|30771] INFO: CurlError[76931fac-9dab-42b3-86c2-48b87d6ae33f^@]: Curl error: Upload failed (at start/before it took off) [./ftp.cpp:345]
void plesk::tFtpConnection::UploadFile(const string&)
[2013-11-29 01:19:42.862|30771] INFO: tRepository::StreamError[1dc709e1-11c7-4e1e-87ac-b6f8cac0bb2f^@]: Stream error: Transport error: unable to put local file /usr/local/psa/PMM/tmp/backup/backup_info_1311290054.xml.tar to backup_1311290054.tar: Curl error: Upload failed (at start/before it took off) [./repository.cpp:356]
void plesk::tRepository::Put(const string&, const string&, bool)


The cause is the lack of available disk space on FTP-server.

If in backup settings the maximum number of backups in repository is specified, the scheme of backup creation in personal FTP repository looks like:

  1. Creation of the backup on the server
  2. Uploading the backup to FTP repository
  3. Removing the oldest backup on the FTP repository (if the maximum number of backups is reached).


Free enough disk space on the FTP server so that it is possible to upload a backup.

Search Words

Curl error: Upload failed (at start/before it took off)

unable to put local file

The dump have been made successfully but can not be imported to FTP due to errors.

scheduled backup

backup issue

Curl error: Failed writing received data

FTP repository

Transport error: unable to send directory to repository: Transport error: unable to put local file

backup manager plesk

Unable to make scheluded backup to ftp external

ed7be2b984f9c27de1d2dc349dc19c6d 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c 85a92ca67f2200d36506862eaa6ed6b8 a766cea0c28e23e978fa78ef81918ab8 29d1e90fd304f01e6420fbe60f66f838 01bc4c8cf5b7f01f815a7ada004154a2 0a53c5a9ca65a74d37ef5c5eaeb55d7f 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7 46a8e394d6fa13134808921036a34da8 bd7fc88cf1b01f097749ae6f87272128

Email subscription for changes to this article
Save as PDF