• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 Issue with NGINX and Apache Crashing

crospa91

New Pleskian
Server operating system version
Debian 10
Plesk version and microupdate number
Plesk Obsidian Version 18.0.46 Update #1
Hi Everyone.
I am using Plesk since a few years now for my little hosting business, but recently I've upgraded my machine and plesk now it's installed on a Debian 10 Machine.
Before it was running under ubuntu, and what I've noticed since the migration is that every time an action get done on a customer domain, the whole apache crashes and take ages to restart putting all the other domain offline.

The server is already updated and working on the latest version of Plesk Obsidian.

To Explain better:
Custom of domain example.com changes the SSL or the parameters of their hosting package, as soon as they press OK on the interface the whole hosting system (Apache I suppose) collapses and I start getting 502 from all the websites hosted on the machine.
the apache graceful restart is on and set at 300 so it shouldn't be that the problem.
I don't remember seeing this behaviour back in the days where the system was installed on ubuntu.

Can someone advise me on what it's best to do to try and figure out this? or am I just looking at an expected behaviour?

Thanks!
 
Back
Top