Resolved [PPP-33003] Backup failing on all Onyx 17.5 installations since last night, CentOS

[Bitpalast]

Onyx 17.5 (not 17.0, not Plesk 12.5)
CentOS 7.4

Backup issue since last night on all Onyx installations for all client accounts that are being backed up to external FTP storage:

Warning: client "<client name>"
"backup_restore_helper utility returned incorrect result. Some settings have not been dumped. Please, contact your service provider"
...

In the backup logs no issues but at the end many of these lines:

INFO: Curl output: * SSLv2, Unknown (23):

Update: This only occured once. It does not seem to be linked to the issue.

Update 2: Done some tests, the error occurs, too, when FTP is used instead of FTPS.

 

[OverWolf]

Hi Peter,
just my 2 cents, but is it possible that SSLv2 is been expressly excluded how SSL protocol ?
Generally, for better security, SSLv2 and SSLv3 is recommended to exclude them.

 

[IgorG]

This issue appeared after the latest WordPress Toolkit update, the error is not fatal, all the data is backed up normally, only today this bug was fixed for Onyx 17.8 - PPP-33003

 

[Bitpalast]

This issue appeared after the latest WordPress Toolkit update, the error is not fatal, all the data is backed up normally, only today this bug was fixed for Onyx 17.8 - PPP-33003

Will it be fixed for 17.5, too? Else we'll now have error messages on all backups every day and won't be able to tell whether the backup is good or bad.

 

[IgorG]

Will it be fixed for 17.5, too?

We have marked this bugreport for including to microupdate, but I have no any ETA when it will be released.

 

[Bitpalast]

Thank you. Hoping on a fast solution for this one.

 

[Bitpalast]

It now has its very own support article A server backup task finishes with the error: backup_restore_helper utility returned incorrect result

 

[Bitpalast]

... the error is not fatal, all the data is backed up normally,

We had to restore a Wordpress website for a customer today. The restore acted as it normally does, but the result was, that no files were written to the target. So either the restore made a mistake (it showed success however) or the files were not backed up. At the moment I am lacking the time for further investigation what the issue is, but I thought you might want to check again, if data is really backed up normally.

 

[IgorG]

Fixed:

Plesk Onyx 17.5.3 Update 32

• On servers with with WordPress Toolkit, having both customer and reseller accounts, creating full server backup completed with warnings. (PPP-33003)

 

[Bitpalast]

And it is back: In Plesk Onyx 17.0 since last night, and on another 17.0 system since last week.

 

[Bitpalast]

And it is back: In Plesk Onyx 17.0 since last night, and on another 17.0 system since last week.

Seems to be fixed. Backups ran error-free last night.