• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Issue Backup to FTPS server fails after upgrade to Plesk 18.0.64

mjehlenz

New Pleskian
Server operating system version
AlmaLinux 9
Plesk version and microupdate number
18.0.64
Hi all!

One of our servers automatically upgraded to Plesk 18.0.64. Since the upgrade the daily backup job to an FTPS server fails with the following error message:

Unable to create the remote backup: Curl error: Unable to finish an upload: (28) Timeout was reached: Last FTP request: APPE backup_2409280008_2410030008.tar: Last FTP response: 125 Data connection already open; Transfer starting: Connection to the FTP server has lost

When we disable FTPS in the remote repository settings, the job runs without problems.

When we try to reenable FTPS in the remote repository settings, the following error message is displayed (I have redacted the hostname of the backup server as well as the username):

Fehler: Datei kann nicht in den Speicher hochgeladen werden: Stream error: /check0/test: Curl error: Unable to finish an upload: (28) Timeout was reached: Last FTP request: APPE test: Last FTP response: 125 Data connection already open; Transfer starting: Connection to the FTP server has lost Überprüfen Sie, ob Sie Berechtigungen zum Hochladen von Dateien im Speicher haben. Sie können dies unabhängig mit den folgenden Befehlen überprüfen: echo 123
When I manually run this command from the affected server, curl successfully connects to the backup repository and creates the directory as well as the test-file.txt.

Does anyone else see this error? Does anyone have any suggestions on how to fix this?

Thanks in advance!

Moritz
 
The command got truncated unfortunately:

echo 123 | curl -T - --ftp-create-dirs -v --ftp-pasv --ssl -k -u ftpusername 'ftp://backup.example.com/./test-dir/test-file.txt' curl -v --ftp-pasv --ssl -k -u ftpusername 'ftp://backup.example.com/./test-dir/'
 
Back
Top