Search results

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.

Since Node.js extension version 2.1, all records are stored in the following file: /var/log/passenger/passenger.log # tail /var/log/passenger/passenger.log [ D 2022-12-07 11:50:40.0046 11270/Tb Ser/Server.h:691 ]: [ServerThr.2] Updating statistics [ D 2022-12-07 11:50:40.0047 11183/Td...

First of all make sure that you have enough free disk space with the command # df -h If free disk space is ok, check other possible reasons for this issue: https://support.plesk.com/hc/en-us/search?utf8=%E2%9C%93&query=QLSTATE%5BHY000%5D+%5B2002%5D+No+such+file+or+directory&commit=Search

Go to Tools&Settings > IP Addresses, click on IP Address and set the domain name of expired domain as Default site. Then go to https://xxx.xxx.xxx.xxx/wp-login.php

Try to apply solution from this KB article: https://support.plesk.com/hc/en-us/articles/360025938354-Plesk-does-not-open-SWKeyExFatalError-Repository-is-not-opened

I would suggest you check SELinux status with # getenforce

We recently prepared a Plesk 18.0.48 image with Ubuntu 22.04 and requested to publish it in the Lightsail. This usually takes some time on their part. I think you should wait for this image to become public.

Just create Add-on Service Plan with PHP 5.x and attach it to the needed customer subscriptions. https://docs.plesk.com/en-US/obsidian/administrator-guide/customers-and-resellers/hosting-plans-and-subscriptions/setting-up-addon-plans.70673/

Multivolume backup is a tar archive sliced into chunks of a certain size. It is to be expected that you cannot unpack one of the pieces of the whole archive. To unpack the whole backup, you must merge all the pieces into one archive first. But to be honest, I don't understand why you need to do...

In case of transfer via backup/restore, all that will be backed up and not backed up are described in the table here: Backup Objects: Hierarchy and Volume You can check that the cloning feature will fit your requirements: Deploying Plesk Servers by Cloning