• 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 Httpd not starting

Hi jesse_mulder,

pls. read and follow the suggestions from:


... as Plesk already has a corresponding Knowledge - Base article with your described issue:

But that is after the update of the package I said earlyer in this thread.
After the reboot the apache/httpd wont start at all.
So that is not the problem, the main problem is that apache wont start after the upgrade of the package called in #13.
 
Hi jesse_mulder,

as next option, you might consider to manually edit the apache webserver - configuration files and edit the mentioned lines in your error message:
line 64 of /etc/httpd/conf/plesk.conf.d/server.conf
... which is not at all a recommened option, but at least you are able to restart apache afterwards, when you removed the corresponding code, which apache deckares as issues/errors.

In addition, pls. consider to open a corresponding bug - report, if you think that the issue is caused by Plesk, it's components or extensions:

 
I stay how it is right now, reverted a backup and maybe in te future reinstal my server :(
Thx for the help.
 
Back
Top