Search results

Fixed in Plesk Obsidian 18.0.49

Fixed in Plesk Obsidian 18.0.49

There is old thread about spamassassin upgrade: SpamAssassin update from 3.3.1 to 3.4.1 This may be helpful.

Try to repair mail and database settings first with # plesk repair mail # plesk repair db

I suppose it would be better to create new VPS with lower resources, install there Plesk with Plesk Web Installer an then perform migration from old Plesk server to new one. After that you can remove first VPS.

Thank you.

Unfortunately, RockyLinux 8 has shown a very low level of demand. However, any supported OS costs Plesk serious development resources and the daily cost of automated testing on the cloud platform. Therefore, support for RockyLinux 9, although considered, is not a priority.

@xainsyed First of all, this is the section of the forum about Plesk for Windows. I advise you to create a new thread about the problem in the appropriate section of the forum. Second, PHP 7.1 has long been in EOL status PHP: Supported Versions and is, therefore, not recommended for...

What do you want to do exactly? Upgrade OS vendor's PHP version of Plesk PHP version?

Very similar to an attack on your server. I think it would be worth examining the fail2ban logs, for example, to get more details.

You only need to install the necessary perl libraries there. As an example it uses yum, the package manager of CentOS. For Ubuntu, use its package manager, apt and the corresponding names of these perl libraries. wget and vim have the same package names. The other commands in this article are...

Please try to use solution from this KB article: https://support.plesk.com/hc/en-us/articles/115000715134-The-System-Updates-does-not-work-in-Plesk-The-System-Updates-tool-is-already-installing-updates-in-automatic-mode-Please-try-later-

Please contact Plesk Support Team. They will fix the issue directly on your server: https://support.plesk.com/hc/en-us/articles/213953025-How-to-get-support-directly-from-Plesk-

@WebHostingAce, developers would like to perform debugging this rare case directly on your server. If you don't mind, please contact our Support Team to give them access to your server for further investigation. Thank you.

Have you tried to repair Plesk installation with # plesk repair installation ?

You have to be logged as root. This fact shows the presence of symbol # and not $, as in your screenshot. Please login as root and show the output of the command: # ls -la /etc/sw/keys/

Check that the service sw-cp-server is up and running. Check that port 8443 listened with the command: # lsof -i tcp:8443 If sw-cp-server service can't be stared, please check log files /var/log/sw-cp-server/error_log and /var/log/sw-cp-server/sw-engine.log

Thank you. The bug was proved PPP-59280

https://support.plesk.com/hc/en-us/articles/360002764993-Why-swap-is-required-on-Plesk-for-Linux-servers-

Sorry, but it is not in my power to predict when Lightsail Team will publish this image. It usually takes a long time on their part.