• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Plesk little bit damaged, how to fix?

PeopleInside

Regular Pleskian
Server operating system version
Ubuntu 22.04.1 LTS
Plesk version and microupdate number
Version 18.0.46
Recently a BUG has create some issues on my server.
I fixed the BUG by removing the file /etc/apt/sources.list.d/plesk-ext-ruby.list but Plesk panel seems corrupted even if diagnosis never find issues.

When I try to install an extension I get this:
1662288758694.png
This was different screen before the corruption and this screen never update stay frozen.
I need exist from this then the extension is installed.

Also if I create a new customer the screen stay frozen in the creation process and need exit from the page to see the customer created.
Any idea on how I can fix this? Need maybe do an update or see Plesk reinstalled without I need loose my server actually active with all websites , emails and services?
 
Probably there is a hanging process in the Linux process list that is related to Plesk or one of their management processes. Subsequent processes will not be started when a running process of the same type has not yet finished. You need to find that hanging process by checking the Linux process list. Normally this is easy to find as you can simply check how long a process has been running and is related to Plesk. Another, more quick and dirty solution could be to either stop all psa service associcated services by
# service psa stopall
and then start them again
# service psa start
(but this is not guaranteed to work) or to reboot the server. The better solution is to find out which process is hanging and to only terminate that one.
 
Probably there is a hanging process in the Linux process list that is related to Plesk or one of their management processes. Subsequent processes will not be started when a running process of the same type has not yet finished. You need to find that hanging process by checking the Linux process list. Normally this is easy to find as you can simply check how long a process has been running and is related to Plesk. Another, more quick and dirty solution could be to either stop all psa service associcated services by
# service psa stopall
and then start them again
# service psa start
(but this is not guaranteed to work) or to reboot the server. The better solution is to find out which process is hanging and to only terminate that one.
Resolved with a reboot, thanks!
 
Back
Top