• 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 Plesk 12 to Plesk 17 breaks my site :(

Kris

New Pleskian
Basically i lost everything, lucky I have back ups. Every time update to Onyx my site breaks, i can see the default home page, however, when i try to log in get an error, i tried about 5-6 times already... any ideas what I'm doing wrong? I'm using the upgrade feature within Plesk 12 - is that wrong?
 
Have you tried to fix your sites with

# plesk repair web

and your whole installation with

# plesk repair installation

?
 
Thanks Igor, actually this thread fixed my problem....

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.

https://talk.plesk.com/threads/afte...-starting-sw_cp_server-service-failed.340992/
 
Back
Top