Search results

The answer is already in this thread

I think they should also update the loaders on the older PHP versions, to enable them to decode files encoded with v12 as well.

Thanks, I had the exact same problem on a fresh Plesk 18.0.33 install.

Yes, this finally has been fixed with the November 30 update. ioncube loaders version 10.4.5 are now shipped with PHP 7.4 and all is fine, finally.

Well, this is not a bug in Plesk itself, but in a third party product that Plesk ships. Last night PHP 7.4 got updated to 7.4.12 and my WHMCS websites went down until I manually updated the ionCube loader again. If I don't replace the ionCube loader that gets shipped with Plesk, my websites...

Username: H9k TITLE zend_mm_heap corrupted with PHP 7.4 and ionCube 10.4.2 PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk 18.0.30 Update #2, Ubuntu 18.04.5 LTS, x64 PROBLEM DESCRIPTION When running WHMCS v8 with PHP 7.4, I get `zend_mm_heap corrupted` errors. STEPS TO...

Thanks! On Linux however, it ships with 10.4.2, which unfortunately is also broken. There is version 10.4.3 meanwhile, that works again. Should I file a new report?

I see it was updated to 10.4.2 with your PHP 7.4.10 release. Thanks! Unfortunately, on the same day ioncube released version 10.4.3 with this changelog: "Fix for a regression in the 10.4.2 PHP 7.4 Loader which could lead to a zend_mm_heap corrupted error with WHMCS." Damn... :(

Sure, done!

User name: H9k TITLE Segmentation fault with PHP 7.4 and ionCube 10.4.0 PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk 18.0.29 Update #1, Ubuntu 10.04.5 LTS, x64 PROBLEM DESCRIPTION When running WHMCS v8 with PHP 7.4, I get segmentation faults. STEPS TO REPRODUCE...

I have many segmentation faults with PHP 7.4 and ioncube files. I see you ship PHP 7.4 with ionCube 10.4.0 loaders. If I manually replace the loader with version 10.4.1, the problems are all fixed. Could you please bundle ioncube 10.4.1 with the next PHP 7.4 update?

Yep it is fixed for me as well Sent from my iPad using Tapatalk

I upgraded to 7.3.1 but it still crashes for me unfortunately...

Hi there! I updated Smarty on the affected websites, so i had no more php errors/warnings on any of them. Still, the FPM crashed twice today so far, ad 11:02 and 21:02. The websites have very little traffic, but each hour at :02 the monitoring task runs, which just does a head request on those...

I enabled debug logging, however it did not crash since... so I will post once it did. I have no widespread application running, just some self made stuff using some libraries like smarty. I checked the error logs and the only error that gets logged is a deprecation notice. However I dont see...

I just have about 8 websites configured on php 7.3 1. It's a real die, the process is not running anymore 2. systemctl status reports "failed", code "killed" and signal "SEGV" 3. journalctl reports no entries 4. site content is HTTP 503 service unavailable 5. will do 6. i don't think so, but...

TITLE: PHP 7.3 FPM dies without a trace PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE: Plesk 17.8.11 Update35, Ubuntu 16.04 LTS, x64 PROBLEM DESCRIPTION: A couple of times per day, the fpm process for php 7.3 just dies, leaving all websites using PHP 7.3 down. The watchdog does not detect any...

Same issue here, would be nice if Plesk would support submodules in the git feature as the feature itself is pretty cool but this is kind of a major setback for my projects...

I can confirm that the mailbox_alias plugin did the trick. In my case, on Ubuntu 16.04, there was no need to install anything. I just created a new configuration file /etc/dovecot/conf.d/24-mailbox-aliases.conf with the following content: mail_plugins = $mail_plugins mailbox_alias plugin {...

Same problem here :( My solution right now is to disable moving spam to the spam folder in Plesk and use a Sieve filter instead...