• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

FTP-Repository doesnt work correctly ..

G

gadrecs

Guest
Hi all,

im experiencing some strange behaviour with my plesk 8.6 backup to FTP functions:

when there is a file stored in the ftp-repository used for backing up my clients and sites
Plesk gives me this error:

P;LESK fatal exception
0: /usr/local/psa/admin/plib/backup/BackupRestoreCommon.php:383
BackupFTPRepositoryDriver->getBackupsList()
1: /usr/local/psa/admin/plib/backup/BackupRestoreCommon.php:81
BackupRestoreCommon->fetchBackupsList(object of type BackupFTPRepositoryDriver)
2: /usr/local/psa/admin/plib/backup/BackupRestoreCommon.php:68
BackupRestoreCommon->getBackupsList()
3: /usr/local/psa/admin/plib/backup/BackupFilesList.php:101
BackupFilesList->fetchBackupFilesList()
4: /usr/local/psa/admin/plib/class.cList.php3:103
cList->fetchList()
5: /usr/local/psa/admin/plib/class.cList.php3:123
cList->init()
6: /usr/local/psa/admin/plib/backup/BackupFront.php:99
BackupFront->stepBegin()
7: /usr/local/psa/admin/plib/PMM/MigrationCObject.php:102
MigrationCObject->make()
8: /usr/local/psa/admin/htdocs/backup/main_client.php:26

There is no difference in storing the files there in subdirs or directly in the "root".
As soon as there is more then the .ftpquota-File it "crashes" with this error.

If you remove all the backup-files in the dir, you can access the backup-dialogue-pages in plesk

I already reinstalled the whole server and updated to 8.6 prior to restoring my backup-files (which i happily copied to another server before ...) but the problem persists.

Any ideas ?


Kind regards,

markus
 
Back
Top