• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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