• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

Apache Server terminates every day

PARALAX

New Pleskian
There is a strange problem since using Plesk with our hoster but only since using Plesk. We never had such terrible outages since Plesk was installed. The problem is following (translated by Google):

"The watchdog and Apache Service monitoring is switched on.
Turn it on Apache from Plesk is automatically switched off monitoring watchdog (Apache service) makes so yes no meaningful"

That's what I should copy because our hoster is not able to communicate in english here. Our website is down every day after some hours leaving the Plesk panel and will only re-activated after logging in and save the configuration in the user panel. BUT WE CANNOT CHECK EVERY DAY AND LOG INTO THE PORTAL TO MAKE OUR WEBSITES AVAILABLE!!!

So please...ANYONE, if you could help us...please DO IT!!!
 
We have exactly to know WHICH Logs. What's the name of the LOG-Filename?

The Web Server (Apache) service on host vserverworld.de is down.
The problem was discovered on Oct 8, 2015 06:38 AM.

The Web Server (Apache) service on host vserverworld.de has been started on Oct 8, 2015 06:40 AM.

That's the only information I got from our hoster and he is obviously clueless as I am at this point.

The problem is still not solved, even with Watchdogs. Apache should be re-activate it but sometimes fails like today.I got an 503 Error on every website until I log into Plesk, go to PHP or webhosting settings and simply save the configuration below. The is defenitely caused by Plesk and we never had such problems before using it!

He is using a usual Root-Server by Hetzner with the latest Debian version.
 

Attachments

  • Error.jpg
    Error.jpg
    159.8 KB · Views: 4
Last edited:
Back
Top