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

Apache gets unavailable on every change

B

BjørnJ

Guest
For absolutely every change I do regarding web hosting in Plesk, be it adding a subscription, changing PHP settings or anything else, Apache gets unavailable for a couple of minutes.

It seems like it is shut down, rebuilds its config then started again. Anyway, it causes a lot of unneccessary downtime.

Is Plesk really supposed to work this way? I am very close to migrating all my customers to a different CP.

I'm running 10.4.4.
 
Thank you for your reply, Igor. This seems to have solved the issue.

For others who may stuble upon this thread:
When I did a full restart of Apache, it would only take a only a second or two, but every change I made in Plesk made Apache unavailable for a couple of minutes.

The solution in the KB seems to not only replace the "apache restart" with an "apache reload" (graceful restart), but seems to also change the order Plesk does it's things. Now I have no downtime at all.
 
Back
Top