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

Domain backup & Rstore problem/Bug?

T

Traged1

Guest
Using PELSK 7.5.1 and RHEL 3, I back up a domain using the CP's domain backup button, then upon attempting to restore the domain, I get this:

START LOGGING: Tue Feb 01 17:04:18

===============================================================================

Attempt to connect to MySQL server ... done

===============================================================================

Checking packages installation ... done
'216.xxx.xxx.16' ip address does not belong to 'austin_axxakxx' client ip pool.

However the actual IP it should be using is '216.xxx.xxx.164' which mean that it appears that PLESK is truncating the last number from the last octat of the ip.

To work around this I have added the IP 216.xxx.xxx.16 to the server but this IP is not really our IP. The backup restoration process then can finish without errors, then you need to switch the IP back on the domain record to the proper IP.
 
Back
Top