• 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 Updater is resetting the SW-CP port

zepho

New Pleskian
Cheers,
I change the default Plesk port usually due to multiple reasons.

For IPv6 I changed the file /etc/sw-cp-server/conf.d/ipv6_ports.inc

But this file will be restored (possibly by the update manager) every night.
/etc/sw-cp-server/conf.d/plesk.conf stays untouched and keeps my port modifications.

In the end: After the update the `sw-cp-server` fails to restart and I have to fix it every day for weeks now! Being more particular: It fails because I set up a port redirection from 8443 to my custom port for localhost calls, to fetch some bad implemented plugin, which are not able to check for the Plesk port before updating themself (MagicSpam for e.g.).

Are you aware of this? In my eyes its clearly a bug. What do you think?
 
Instead of a cron job you can maybe create an event "after update" to run a script that applies custom changes to the files after each update.
 
Back
Top