• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Litespeed registration changes IP address

Daveo

Basic 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