Search results

Both the XML and the tzst files are needed to restore a backup. In the CLI command use only use the XML file to import the backup.

The xml file should be used.

Are there any error messages shown about renewal?

I suggest opening a ticket with our support team for an investigation of the issue. To sign-in to support and open a ticket go to https://support.plesk.com. If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is...

If you can't login to Plesk, but still have SSH access to the server, you can use the CLI to restore a backup. This article describes the CLI command you can use in more detail: https://support.plesk.com/hc/en-us/articles/12377586491927-How-to-restore-a-Plesk-backup-from-CLI However, note that...

This line SOURCE = http://autoinstall.plesk.com/plesk-php8.3 in your /root/.autoinstallerrc file indicates that an earlier Plesk version was updated with experimental PHP 8.3 support. This is likely prohibiting you from upgrading. Before you make any changes make sure to make a backup. You can...

Not to my knowledge, no. If you feel that an auto-migrate feature is missing from Plesk don't hesitate to add it a suggestion on our UserVoice page. Features that become popular might be considered for implementation into Plesk.

What's the output of grep SOURCE /root/.autoinstallerrc and cat /etc/yum.repos.d/plesk.repo?

You mean a backup stored on the Plesk server? Or on your own computer/laptop?

Hi, I suggest opening a support ticket with out support team for an investigation of the issue on your server. To sign-in to support and open a ticket go to Plesk. If you got your license from a reseller, your reseller should provide support for you. If the reseller does not provide support...

According to user, his issue was related to mod security. As far as I can see there are currently no issues related to Roundcube known to us. (FWIW I have been using v1.67 without any issues in production for about 3 months now).

Hi, you can use the 1st option from the resolution mentioned in this support article: https://support.plesk.com/hc/en-us/articles/12387409609495-Unable-to-run-scheduled-backups-or-run-Migration-on-Plesk-Access-denied-for-user-admin-1-using-password-YES

I recommend to open a support ticket with our technical support team to have them investigate the issue on your server. To sign-in to support and open a ticket go to https://support.plesk.com. If you got your license from a reseller, your reseller should provide support for you. If the reseller...

I see that you've contact our support team and that they have been able to resolve the issue for you. Is that correct?

I am not sure. I recommend to open a support ticket with our support team for an investigation of the issue. To sign-in to support and open a ticket go to https://support.plesk.com. If you got your license from a reseller, your reseller should provide support for you. If the reseller does not...

I don't think so. However I might be best to manually update the server to Plesk 18.0.63.

If you got your Plesk license(s) from your provider they have enabled ELS (Extended Lifecycle Support) for you, which allows for prolonged CentOS 7 support and updates. I am not sure why you haven't had any updates (yet) for your AlmaLinux server(s). Don't hesitate to open a support ticket with...

There is no comparable feature available on Plesk for Linux. Migrate email to Plesk the Plesk Migrator is available, which you can configure to migrate from a custom environment. Alternatively you can create your own migration solution using the Plesk CLI utilities, or the XML-RPC and REST...

Hi there, I am not sure if I understand why you want to downgrade your PHP version. Plesk allows you to install and use multiple PHP version on your server. Which can be used via command line to. Calling the php uses the default PHP version shipped with your OS. If you want to use any of the...

@Dmytro the errors shown on the log of your screenshot are not caused by the "Block access to potentially sensitive files" option from the WP toolkit. (Because in that case the errors would get logged in the Nginx logs.) Instead these errors are (most likely) caused by the .htaccess...