Search results

Hello, @JuanCar . We have a registered bug for this behavior identified with ID EXTNODEJS-135. Unfortunately, at this point, I cannot suggest a workaround for removing the inactive domains from the list. The issue will be fixed in one of the future releases, but I cannot provide an ETA. You can...

Hello, @chazza . To me, it sounds like the Default Plesk Interface is set as Power User view for the license in Partner Central. If you are a Plesk partner, please check the configuration in your Partner Central: Product Configurations If you purchased the license from a third-party Plesk...

Unfortunately, at this point, there is no way to cover the site preview URL with valid certificate. I will need to check further why you are being prompted to buy the SSL again and how could that behavior be potentially avoided. I will follow up with more details as soon as possible.

If the records are for a second-level domain like example.com (as it looks like from the attached notification), the DS records should be added through the domain registrar, i.e. the provider from which you bought the domain name. If they are for a subdomain of a domain hosted in Plesk and...

Thanks, Peter. I opened a new internal report, so our team can double-check in case I am missing something. If they are also unable to reproduce the error it will be best if you can provide us with access to narrow down the reason.

It is not handled automatically. The keys must be manually updated in the parent zone. If you are unsure where the parent zone is, you can use a tool like DNSViz. If the records are not updated you can experience DNS issues, so I wouldn't recommend ignoring the notification. The full doc...

No, your setup is right. If you want to cover examplesitename1.123-456-78-90.previewdomain.com it should be for 123-456-78-90.previewdomain.com. I believe the new aliases should be automatically covered by the SSL, but since you are asking I am guessing that doesn't happen. What you can try is...

Hello, @GreenhouseTech . Do I correctly understand that the wildcard SSL is installed for *.123-456-78-90.previewdomain.com rather than *.previewdomain.com?

It could be. I tried disabling the functions globally and still no such error: Would you mind testing that on a default WordPress installation?

Thank for the update. The functions are disabled (checked with phpinfo). I deleted some tables and files prior to the restoration, switched the language to German, but still I am unable to reproduce the error. What's the MariaDB/MySQL version you are running?

https://support.plesk.com/hc/en-us/articles/12377019825559-Is-it-possible-to-update-curl-on-Centos-7-or-Ubuntu-18-04-server-with-Plesk

Thanks for the report, Peter. I am unable to replicate the error. What's the PHP version and handler you are using?

Thank you. Could you please review the scheduled tasks for the account you are trying to backup and double-check if there are any cron jobs with unrecognized characters?

I am afraid this is not possible, @Mark_NLD . Regarding the notifications our PMs forwarded the feedback to CloudLinux and the ETA for the expected improvements was set to end of Q2. I will double-check if we can provide any further details if there are any changes. Unfortunately, we are not in...

Hello, @sgm . Unfortunately, this error alone doesn't provide enough information to suggest what might be causing the issue. Please inspect the backup log and let us know what's logged in it.

Our team informed me that the rollout of the Imunify extension hasn't officially finished yet. In other words, you are both affected by the issue I explained above. Please note that the extension wasn't intentionally installed on your servers and Plesk is not trying to force the Imunify...

@valwello , the Plesk upgrade tool would typically update MariaDB to the latest supported version. I believe, 10.11.11 is not present in the official MariaDB yum repository for CentOS 7.9. I would suggest considering an upgrade to another OS.

@KAEL We have an existing bug with id PPPM-14983 and our team is currently working on it. I cannot provide an exact ETA at this point, but I believe the fix will be released relatively soon. You can monitor the changelog here. In the meantime, the workaround we can suggest is running: That...

Hey, Andreas. I messaged you privately since we will need some details that shouldn't be publicly disclosed.

@EduardoG , @Quinten , the fix for the issue has been published in Microsoft Azure DNS version 1.2.2-5841. You may proceed with updating the extension.