• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

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