• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Issue Litespeed registration changes IP address

Daveo

Regular Pleskian
Server operating system version
Debian 11.8
Plesk version and microupdate number
18.0.57 Update 3
Hi.

We have two IP addresses registered within Plesk.

IP 1 is used by Plesk and two other sites.

IP 2 is used by one site.

We have litespeed extension (v1.4.19-0) installed and licenced (thru litespeed to IP 1), if the site on IP 2 makes a change on his site thru Plesk (like a restore) then the litespeed IP address for registration changes from IP 1 to IP 2 and causes litespeed to be in an unregistered state and stops all sites on the server from working.

Any ideas on how to stop/prevent this from occurring ?
 
Back
Top