Search results

Nevertheless is there an ETA for this bug? It would be great to have a fix in "Plesk 18.0.51 Update 1" as right now this is a main blocker for any upgrade of live systems.

@Peter Debik You made my day. Our issue was caused by the problem you did describe.

We can confirm that as of March 22, 2023, the issue with Google nameservers on that domain still exists intermittently.

We are not sure if this is related to this bug but we have on top the following issue on our test servers where we did roll out this upgrade: - when trying to create a password protected directory + user the Plesk GUI could not finish the operations and we got timeouts plus the changes were not...

The switch did happen silently already for Plesk Obsidian 18.0.50. Thanks @TeamPlesk!

Hello, on some of our Plesk servers we have a strange behavior of the Plesk Backup Manager. If a subscription is bound to a chrooted shell or SSH access is even forbidden, a backup (e.g. only configuration) will create the .ssh directory in the subscription including SSH keys (id_rsa +...

@Peter Debik Thanks for your quick work around that did the job for us. In our case the problematic PHP handlers were still used in some service plans as default PHP handler.

We have the same issue also with PHP 7.4 on our servers with the latest Plesk version 18.0.49 Update #2.

Let the games begin: CVE-2022-31631 PHP Bug #81740 (PDO::quote() may return unquoted string) And still no ETA when Plesk will remove PHP 7.4 from its core.

@CobraArbok There is a Plesk article dealing with your issue: How to add a custom PHP version in Plesk for Linux?

@ghazestor We did not experience any increased CPU total usage. Based on your settings the free workers are not the ones to blame. The speed increase comes from the dedicated master processes per website having their own OPcache. This can improve PHP performance dramatically by storing...

@ungov Yes this is possible. It's a bit hidden and only documented in this Plesk article: How to add a custom PHP version in Plesk for Linux?

@IgorG This sounds like we are many months away from PHP 8 compatibility even though PHP 8 was released two years ago. Will Plesk at least provide backported security fixes to its PHP 7.4 handlers?

PHP 7.4 reaches end of life in 9 days (28th of November 2022) and I am wondering about the progress of PHP 8 compatibility in Plesk Obsidian. As of today Plesk Obsidian 18.0.48 is using PHP 7.4 as default PHP handler in various ways: - PHP 7.4.32 is used by Plesk itself for e.g. the admin...

The article mentioned does work for us. We did switch to PHP 8.1. Just point 7 of the tutorial is wrong. plesk repair web -domains-only ... is needed as last step instead of: plesk repair web -server ... to regenerate the Apache webmail configuration files under...

Our clients are using the address book of Roundcube. This makes a drop-in replacement very hard. Now we are testing to setup a new PHP handler for webmail as described in the following Plesk article: How to change PHP version for webmail in Plesk for Linux.

@IgorG PHP 7.4 is end of life on November 28th 2022 (in 9 days). As our security policy does not allow to use unsupported PHP versions we have now the trouble, that we would loose Roundcube Webmail support on our servers as the package still depends on PHP 7.4. Will there be a Plesk update...

Related to the original topic I have to add, that I did not overlook the change of the trial policy. Plesk added it later to the changelog of Plesk Obsidian 18.0.47. The "Wayback Machine" did sort it out Plesk Obsidian 18.0.47 - web.archive.org - 28/09/2022. The red "pay attention" is missing in...

Our Plesk partner did just send us the information about the new prices starting from 01/2023 onwards. For us the license costs will increase between 12 and 22% depending on the edition used. We really hope that the extra money is used to make Plesk more stable. There are a lot of open bug...

If this is the new expected behavior it would be nice for the Plesk users to be informed about it in the changelog or by a new warning before the upgrade process. Also in the past before Plesk Obsidian 18.0.46 the admin could decide whether or not to take the risk. Workaround to avoid the new...