Articles in this section

See more

NextCloud and Typo3 applications are not stable on Plesk PHP 7.2.32 and 7.3.20

Avatar
Benjamin Wessel
Updated
Follow
Plesk for Linux kb: bug ABT: Group B

Applicable to:

  • Plesk for Linux

Symptoms

  • NextCloud or Typo3 applications are not accessible with webbrowser, one of the following HTTP status codes is shown:

    CONFIG_TEXT: Server Error 500 Internal Server Error

    CONFIG_TEXT: Server Error 503 Service Temporarily Unavailable

    CONFIG_TEXT: Server Error 502 Bad Gateway

  • Plesk PHP 7.2.32 or 7.3.20 is configured in Domains > example.com > PHP Settings > PHP version

  • The following errors are shown in the Plesk PHP log files:

    CONFIG_TEXT: WARNING: [pool example.com] child 27146 exited on signal 4 (SIGILL) after 0.649431 seconds from start

  • The following error is shown in the log files /var/log/messages (CentOS-based) or /var/log/syslog (DebianOS-based):

    CONFIG_TEXT: kernel: traps: php-fpm[27146] trap invalid opcode ip:71222d sp:7ffcbc457820 error:0 in php-fpm[400000+400000]

  • Running the following command shows the same error message:

    # /opt/plesk/php/7.2/bin/php -r "echo 'Argon2i hash: ' . password_hash('pwd', PASSWORD_ARGON2I) . PHP_EOL;"
    Illegal instruction

    # /opt/plesk/php/7.3/bin/php -r "echo 'Argon2i hash: ' . password_hash('pwd', PASSWORD_ARGON2I) . PHP_EOL;"
    Illegal instruction

Cause

Product issues:

  • #PPPM-12210 "Argon2 usage in PHP 7.2 and 7.3 causes crash due to "Illegal instruction""
    Fixed in:
    • Plesk Obsidian 27 July 2020

Resolution

Please consider updating your server:

Note: If PHP downgrade was applied with script for Debian 9 or Ubuntu 16 follow these steps:

Plesk Obsidian on Debian 9 or Ubuntu 16, 18

To undo workaround, perform these steps:

  1. Connect to the server via SSH

  2. Run this command:

    # rm -f /etc/apt/preferences.d/plesk-php73 /etc/apt/preferences.d/plesk-php72

  3. Enable Plesk updates:

    # plesk bin server_pref -u -autoupdates true

Comments

1 comment

Sort by Date Votes
  • Avatar
    Eric Matt (Edited )

    Benjamin Wessel, thanks só much for posting this. Was deep down the rabbit hole to figure out why the hell my NextCloud instance wasn't working anymore.

    I was getting "502, Bad Gateway", returns from NGINX on my browser, while running PHP-FPM 7.3. But also on Apache or PHP-FPM 7.2 the same error showed up. It puzzled me that with wrong logins it kept serving me pages, but with correct logins in the webinterface of Nextcloud, it gave me the 502, Bad Gateway error.

    Man oh man, I was having this for two weeks and in some evenings trying to fix it, unable to. Until this post came along. Thx a bunch.

    I added some terms in my comment like the Bad Gateway, hopefully others will find this post as well. Or even better: Plesks brings out a fix...

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles