• 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.

Apache won't start | 10.4.4 MU#32

fearz

Regular Pleskian
Hi,

I was trying to update the plesk control panel SSL since it expired, but it never took the new certificate, always showed the old one which was expired,

I received several emails on daily basis mentioning that Plesk control panel SSL will expire..it mentioned the files as well..

so I edited each file with the new SSL Cert .. now httpd fails to start (Starting httpd: [FAILED])

The files i edited:

pico /etc/ssl/certs/secureplesk.crt 888 pico /etc/ssl/certs/secureplesk.k 1002 pico /etc/ssl/certs/secureplesk.crt 1003 pico /usr/local/psa/var/certificates/cert-Wvyas3 1004 pico /usr/local/psa/var/certificates/cert-fsKjp4 1006 pico /usr/local/psa/var/certificates/certpyD5984 1007 pico /etc/ssl/certs/secureplesk.crt 1009 cd /etc/ssl/certs/ 1011 cd /usr/local/psa/var/certificates 1013 pico /usr/local/psa/var/certificates/certpyD5984 1015 pico /etc/ssl/certs/secureplesk.crt 1016 pico /usr/local/psa/var/certificates/certpyD5984

/var/log/httpd/error_log shows this on each attempt to start /etc/init.d/httpd start:

[Sat Jun 02 07:16:09 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:18:07 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:21:17 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:21:27 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:21:44 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:22:38 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:23:33 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:23:42 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:24:41 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:26:24 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:26:26 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:28:08 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:33:14 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:33:16 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jun 02 07:33:17 2012] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)

OS: Centos OS

Thanks for your support
 
Last edited:
SSL Certs

Why did you edit it by CLI when you could have just done it through the actual GUI and pushed a button and then used the CLI to restart the httpd?

#SERVICE RESTART HTTPD
 
Back
Top