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

Resolved Version 17.5.3 Update #14 > Update #15 killed Plesk

greg2017

New Pleskian
Hi there
I am runing Debian 7.11‬
Plesk OnyxVersion 17.5.3 Update #14
and started the Update #15 - took quite long and after 30min the plesk URL was not reachable any more.
So I can not log in with plesk.
https://root797.premium-rootserver.net:8443/
But server is runing.

I restarted Apache and MySQL without results.

Can I restart the server using the shell?
How can I kill the not finished update files and do I need to do that?

Thanks for your help, Greg
 
Last edited:
Hi greg2017,

pls. note, that Plesk uses its very own webserver called "sw-cp-server" with the PHP-FPM service called "sw-engine-fpm".

You have two choices to restart the related services:

Code:
service psa restart
or
Code:
service sw-cp-server restart
service sw-engine-fpm restart


To investigate the root cause of a Plesk webserver issue/error/problem, pls. have a closer look at the related log - files.

=> /var/log/sw-cp-server

=> /var/log/plesk/install

=> /var/log/plesk/panel.log
 
Thanks, UFHH
we found the error and installed the updates.
will save your commands
Thanks and hi from Weil am Rhein ; )
Greg
 
Back
Top