Search results

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.

@KAEL , I was able to replicate the behavior and I am currently consulting with our team about this case. I will follow up with more details.

@se2e-dev , yes, you are right. You can cancel the subscription at any given moment and renew it in future if required without any outstanding payments. Considering the issue occurs only on one server indicates that the issue is likely related to the local configuration. However, that needs to...

Thank you for the update. I am still unsure what could be causing the issue. I would suggest opening a ticket with Plesk support for further investigation on your server. To sign-in and open a ticket please go to: https://support.plesk.com If you got your license from a reseller, your...

That issue was fixed in Plesk Obsidian 18.0.70. Please let us know if you are still experiencing any issues after the update.

@EduardoG , we have a registered bug identified with ID EXTPLESK-9063. The ETA for the fix is within 24 hours. At this point, I cannot suggest a workaround. I will follow up with more details as soon as possible. Thank you for your understanding in the meantime.

Hello, @chazza This usually happens there is a custom configuration applied on the license installed on your server. If you are the Plesk partner, please check the configuration in your Partner Central: Product Configurations If you purchased the license from a third-party Plesk partner...

Sorry, I am not entirely sure what you meant by "without license activation". If your Plesk license expired, you should still be able to run the pleskbackup utility. If that's not the scenario you are referring to, please provide more details so we can avoid misunderstanding.

I am not quite sure I was able to understand what the issue is. Please provide the exact error you are encountering, the transfer settings of your FTP client, and as many details as possible in general.

I will consult with our team about the issue so we can attempt to reproduce it and further investigate it. Just to make sure I understand correctly, you are also experiencing issue with the login button not functioning and you are getting blocked after successful login attempts? For the time...

I think the auto-respond option in Sogo relies on Sieve scripts, therefore, this won't be applicable. I might be mistaken, of course, and it might be worth it to give it a try. There's no public documentation explaining this particular configuration.