Search results

Hey, I'll allow myself to put an update on it as I fell on it from Google and found a close solution. Thank you for this topic and insight, it had me found the issue. Following command showed and error in "Sury" repo: the key was obsolete since quite a few time: plesk sbin pum --check Fix...

@Peter Debik My bad, backup was done right before the update it seems! I was confused because of timezone differences that may occur, but here it's all in the same timezone and I didn't receive any more failures on the two next days! So I confirm it's all good now! Thank you very much...

Running latest Plesk, tonight's backup still ended with a warning email: "Unable to back up domain keys. Error: Unable to find service node for web service on domain with id=39" (details of my config in my previous message)

Tested it on three of my own websites, no deprecation or error in logs. Even on the WooCommerce one. Using only very well supported scripts though. Performance seems similar so far with PHP 8.2 and 8.3.

Nice!

For sure it will take time for scripts to be updated. Especially if running WooCommerce, since they just fixed PHP 8.1 deprecations a few months ago. But even if not used on all websites, it is important to allow for the latest PHP version for the more technical hosted customers that always like...

It is always good to provide the latest PHP version to customers as fast as possible. Gotta be top of the notch. Newer PHP versions are usually more secure, faster to execute code, and enforce cleaner ways of coding PHP scripts. And from a marketing point of view, it's great to provide latest...

Hi, @Nikolay Contributing to the error debug as I've got a similar issue. It looks alike but the cause is different in my case. Context: I've got a domain (lrob.cloud) with web hosting set to "none" the website is on another Plesk server. It has emails enabled with a mailbox. Problem: Global...

I saw that on release day. Was so excited! So, is dist-upgrade officially supported now? Or just fresh installs?

Good news, right for WP 6.4! Any chance we can learn more about the root cause for the bug? Because it's still weird that it's linked to Elementor.

Good finding. 5 months since Debian 12 release. Usually Plesk takes 6 months to support new Debian releases if I recall correctly. So... Likely one month max to go. Hopefully. I'd be happy already if it went down to 2 or 3 months. Especially when distro changes are pretty minor as with Deb 11->12.

Hello, Sorry to bump this. Just to add a more Linux server mentality to this latest post which I keep falling on by Googling. I've upgraded 9 of my Debian 11 to Debian 12 servers flawlessly. No errors, no hassle, no package dependency problems... Only one config file to edit on a few DNS...

Exactly, to me it's a WP Toolkit bug. Maybe there is a PHP class overlap or something. If that is the case, both of them didn't prefix their classes as advised in WordPress's guidelines. And even more strange, how can a script inside the website alter WP Toolkit's behavior? To me seems like a...

Thank you for looking into it. Did you try disabling DNS zone, or removing the domain entirely? Removing works, disabling does not. So I've tested again and in my config I can confirm it does not work as expected. I've added a "testdomain.tld", disabled its the DNS zone, and tried to query it...

Hello, thanks for your interest. Version on master (Plesk server) is latest from Debian 11: # named -v BIND 9.16.44-Debian Versions on slaves are latest from Debian 12: # named -v BIND 9.18.19-1~deb12u1-Debian So if I understood well, it should perform a "-clean" but it doesn't. Bug?

For my part I don't use Elementor, because as we can see it's junk code that breaks every now and then for various reasons, and it also goes against WordPress's original design. But my customers use it and I'm facing this bug with PHP 8.2 and latest Elementor... The bug also happens when...

Hello, Sorry to bother and up this issue, but here is a related one @AYamshanov @IgorG When you disable a DNS zone, Plesk should also remove it from slaves. Otherwise you get spammed by this kind of entries on slave's DNS logs: Apr 11 22:06:38 ns1 named[3064945]: transfer of 'domain.tld/IN'...