• 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.

Question Wrong command and checks to do before restarting server

E42

New Pleskian
Server operating system version
Debian 11
Plesk version and microupdate number
Obsidian
Hello,
There was a moment when I used the command "plesk bin cloning" and later realized that's not what I wanted.

Now, what I want is this: to be able to restart the server and be sure that everything works fine just like now. So, to "undo" the previous command, I used this one:
plesk bin cloning -u -prepare-public-image false -reset-license false -reset-init-conf false

Is this enough? How can I be sure that after a restart nothing will be erased? Thank you and kind regards
 
hello @E42 ,

first of all I'd recommend you to create full Plesk Backup (Tools & Settings > Backup Manager), just in case.


you can check that cloning was canceled by commands below:
:~# plesk bin cloning -s
0
:~# plesk bin cloning -i
prepare-public-image: false
reset-license: false
update-master-key: false
reset-init-conf: false
skip-update: true
maintenance: false

after that I was able to reboot my test Plesk server and everything fine.
 
Back
Top