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

    https://survey.webpros.com/
  • On Plesk for Linux mod_status is disabled on upgrades to improve Apache security.
    This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.

Issue Backup invalid input parameters in '--make-dump', attribute 'include-server-settings' is not allowed

frundaa

New Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
18.0.74 Update 3
Dear Pleskies,

after update to 18.0.74 (Debian 10) following error occurs:

Fehler: Der Backupvorgang ist fehlgeschlagen: Invalid input parameters in '--make-dump' command: Error 1: :1:0:ERROR:SCHEMASV:SCHEMAV_CVC_COMPLEX_TYPE_3_2_1: Element 'backup-options', attribute 'include-server-settings': The attribute 'include-server-settings' is not allowed.

I have tried

plesk repair -all

and

plesk repair fs -verbose

but does not fix this issue.

Log shows some errors:
Some files packaged by Plesk have incorrect permissions ........... [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Repairing incorrect permissions ................................. [2026-01-01 19:12:31.305] 130109:6956b90b78240 ERR [util_exec] proc_close() failed ['/opt/psa/admin/bin/fsmng' '--fix-plesk-packages'] with exit code [1]
[FAILED]
- fsmng failed: ERROR: Unable to update packages index: Command
'/usr/bin/apt-get update -o
Dir::Etc::sourcelist=/tmp/tmpk55ib069' returned non-zero exit
status 100.

How can the issue be solved. Backup at the moment not possible and a migration to a new server (Debian 12) not possible!
 
Really? Untouched Plesk Image, “auto updates”, nothing changes manually and “one Plesk update” destroying our server! Support from Plesk? Nothing! You are kidding me!
 
Hi, @frundaa . Similar issues are typically caused by incomplete Plesk updates. What I can suggest is trying to run the update manually with the command below. Just to be on the safe side, please make sure you have a backup copy of the server in case something goes wrong.

Code:
plesk installer --select-release-latest --upgrade-installed-components

If the issue still persists, I would suggest opening a ticket with Plesk support for further investigation on your server. To sign-in and open a ticket please go to:
If you got your license from a reseller, your reseller is in charge of providing you with support. You can raise the inquiry with them and they can forward it to our team for further processing.If the reseller does not provide support, here is an alternative to get support directly from Plesk:
 
Back
Top