• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

restoring domains

W

webrebel

Guest
Welp, my server has been compromised and my datacenter is going to reload the OS, (RH ES3 Plesk 7.5.1)

I have backed up all the domains to a remote FTP server in the Plesk GUI, my question is what is the best way to restore? I'm thinking of adding the clients back, then add each domain with no hosting and setup the backup in each to recognize the ftp server, then do a restore. Sound feasible?
 
jeez...no answers huh? Well I feel like I'm on the dark side of the moon at the moment...server is down, waiting for OS reload to finish.

The good news is most clients are understanding of the situation. If I don't bring them back real soon I'm sure that could turn into an angry mob.... ;)
 
5 hours into OS reload. 3 hours ago they said all they had to do was install PLESK....that's the last I heard. Called and they said there was a problem installing Plesk...garsh. Imagine them having a problem with installing Plesk.... :rolleyes: no way :eek:
 
The best way would be to mount the compromised hard-disk as secondary and copy across Plesk data. 3hrs for a Plesk install is a bit over the top for experts - you sure this isn't theplanet? They seem less intelligent than monkeys most of the time.
 
Back
Top