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

Resolved After updating plesk panel from 12 to 17 -> Starting sw_cp_server service... failed

Giovanni

New Pleskian
Hi folks,
I am running plesk panel on my vps. I just decided to update from 12 to 17 from the panel itself.
After the update I am no longer able to load the page of the panel in the browser.

When I try to restart plesk from command i get this:

[root@xxxxxxx ~]# /etc/init.d/psa start

Starting sw_engine service... done

Starting sw_cp_server service... failed

Starting mysql service... already started

Starting named service... already started

Starting mailer service... done

Starting spamfilter service... already started

Starting drweb service... done

Starting tomcat service... not installed

Starting apache service... already started

Starting xinetd service... already started

Then, if i try to restart only sw_cp_server service I get this:

[root@xxxxxxxx ~]# /etc/init.d/sw-cp-server restart

nginx: [emerg] "ssl_ciphers" directive is duplicate in /etc/sw-cp-server/conf.d/ssl.conf:1

nginx: configuration file /etc/sw-cp-server/config test failed

Do you have any suggestions to how fix this?

Thanks and regards.
 
Check the content of /etc/sw-cp-server/conf.d/ssl.conf . Does it contain the ssl_ciphers directive more than a single time? Then remove the additional line. If it only contains the directive once, the same directive is listed in another nginx configuration file. This can be anywhere. In that case you could try
# grep -R "ssl_ciphers" /etc/sw-cp-server/conf.d/*
to check other files in the same directory whether they contain that directive, too. For Nginx each directive must only exist once.
 
I also found this to resolve the problem

# service sw-cp-server restart
sw-cp-serverd: nginx: [emerg] "ssl_ciphers" directive is duplicate in /etc/sw-cp-server/conf.d/ssl.conf:1
sw-cp-serverd: nginx: configuration file /etc/sw-cp-server/config test failed
Cause
This is a software issue with internal # PPPM-3228 .

Resolution
Remove /etc/sw-cp-server/conf.d/ssl.conf file and restart sw-cp-server service:

# rm -f /etc/sw-cp-server/conf.d/ssl.conf
# service sw-cp-server restart
 
Back
Top