Facebook
Twitter-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
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.
Resolved Adding and removing websites/aliases etc can it be improved?
- Thread starter NateWon
- Start date
Yes, the solution for this is to tell Plesk to use "graceful" restarts.
How to enable/disable Apache graceful restart in Plesk
How to enable/disable Apache graceful restart in Plesk
NateWon
Basic Pleskian
Thank you Peter, are there any issues with using NGINX as a proxy and this method.
NateWon
Basic Pleskian
Thanks for the reply, this refers to some issues, its not something I've experienced with Apache, but wondering whether this is of concern.
Is your recommendation to set the graceful restart and you have had no issues with this?
My recommendation is to use graceful restarts whenever and wherever possible. This is an important setting, because else, on each reconfiguration all Apache instances will briefly stop until Apache is restarted, interrupting web server operations for a short time.
The "issues" the article means is probably parallel reloads/restarts of Apache. When you reload the web server configuration while another reload process is already ongoing, Apache can fail and needs to be restarted manually. With a restart interval that is longer than the time an Apache reload/restart needs this is unlikely to happen. It still happens on some occasions, but for these rare moments, you have a script like the Plesk built-in watchdog that can restart Apache automatically, or a home-made script that checks the Apache status more frequently. The later is what we do here, every 10 seconds, but this is entirely up to you and needs some programming.
The "issues" the article means is probably parallel reloads/restarts of Apache. When you reload the web server configuration while another reload process is already ongoing, Apache can fail and needs to be restarted manually. With a restart interval that is longer than the time an Apache reload/restart needs this is unlikely to happen. It still happens on some occasions, but for these rare moments, you have a script like the Plesk built-in watchdog that can restart Apache automatically, or a home-made script that checks the Apache status more frequently. The later is what we do here, every 10 seconds, but this is entirely up to you and needs some programming.
