• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Plesk 12 --> 17 update --> Panel Problem

futureweb

Regular Pleskian
Hello,

I just upgraded one of our Plesk 12 Servers to Onyx.
After the upgrade "sw_cp_server" Service refused to start (Starting sw_cp_server service... failed) ... checked all Logs but they did not indicate any Problem ... after some deeper investigation I found out that "ssl_ciphers" was set twive within sw-cp-server configs - and that this caused the startup problem ... (/var/log/plesk/sw-cp-server/error_log - 2017/02/06 18:30:16 [emerg] 6944#0: "ssl_ciphers" directive is duplicate in /etc/sw-cp-server/conf.d/ssl.conf:1)
If I remember right this change was suggest because of POODLE Attack?!? (not 100% sure)

CT-361-bash-4.1# grep -ri "ssl_ciphers" /etc/sw-cp-server/conf.d/*
/etc/sw-cp-server/conf.d/pci-compliance.conf:#ssl_ciphers HIGH:!aNULL:!MD5;
/etc/sw-cp-server/conf.d/ssl.conf:ssl_ciphers HIGH:!aNULL:!MD5;

Would be good if installer would check for such Problems ...

Bye from Austria
Andreas
 
Last edited:
As possible workaround just comment ssl_ciphers in /etc/sw-cp-server/conf.d/ssl.conf:

# grep ssl_ciphers /etc/sw-cp-server/conf.d/ssl.conf

#ssl_ciphers HIGH:!aNULL:!MD5;
 
Hi Igor,
already commented out one. (commented pci-compliance.conf - would it better to comment ssl.conf??)
Mainly made this Thread to help others if they encounter this problem - and to alert you of this potential issue :)
Andreas
 
Have just come across this on our server;

Commented out as follows
#ssl_ciphers HIGH:!aNULL:!MD5;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
#ssl_prefer_server_ciphers on;

As both were in the pci-compliance.conf file
 
Back
Top