Recent content by LRob

You are both right. Every ionCube version comes compatible with every single PHP version. And latest at the time of writing is 14.4.0. Link: ionCube Loader - Configure for your website to run protected PHP code Original file: Updated file: An update within Plesk packages would be handy and...

So I can confirm manually updating ionCube fixes the issue for my case (an old broken authentification for symfony, causing segfaults and 503 errors). But ultimately the problem is that the embedded ionCube in Plesk's PHP 7.4 is obsolete... More obsolete than PHP 7.4 itself. So this should be...

Glad you like it mate! I've even improved it further now, it manages the reported IP list fully on its own to better "know" which IPs have been reported or not. It's way more accurate, and even handles the cases when AbuseIPDB quota has been exceeded.

It's 2025, 10 years later, and there seem to still be the same limitation with the latest Plesk versions. Resellers or customers can't change nginx directives... Also custom directives applied to their service plans as global admin are not actually applied. Meanwhile Plesk licenses costs 3...

In PHP's book, PHP 8.3 to 8.4 is already a major version change. Minor versions are like 8.3.13 to 8.3.14. I guess Plesk team is compiling and testing newer PHP version only after the final release. So that takes some time. That said, I would still like to see quicker support for latest PHP...

I hope it comes up next week! Given the price Plesk now costs, we need at least to make it worth by bragging about already supporting the latest PHP version

Since PHP 8, Plesk generally supports latest PHP versions around 7 to 14 days after release. Should come up soon. :)

Perfect mate! I just learned a beautiful expression (mutually helping each other, that's a nice way to say it). Feel free to fork, modify, pull request it! All the best.

@brother4 Thanks for sharing the initial script! Since your script was used as a base for mine, do you want to be credited differently from the current "brother4 from Plesk forums"?

Hi, I've improved the script, with working IPv6, better speed optimization, better categories and descriptions, and better handling of cases where a jail is disabled. https://github.com/UltimateByte/plesk-tools/blob/main/report_abuseipdb.sh

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!