• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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