Strange ERROR 500 when update to v1.2.0

Walys

I am working in Shared Hosting with Cpanel

In my forum setting I have: Flarum v1.0.4 with PHP 7.3.33
In Shared Hosting: info server: PHP 7.3.33
And in Cpanel/ MultiPHP option for domains I have working with Flarum have: PHP 7.3.33

All working ok! Now go with Backup and updates....

Now go to review and update the PHP
In my Shared hosting info server: PHP 7.4.27 (This data not possible update for me)
In Cpanel/ MultiPHP option I select my flarum domain and change to PHP 8.0 (ea-php80)

1º First change In composer.json set the versions for all extensions to "*".
2º Review and update all extension.
3º Go with update core: composer update command and php flarum migrate

And... ERROR 500 and all OFF in the web.

THE CHANGE TO MIDDLE SOLVE THIS ERROR:
In Cpanel/ MultiPHP option I select my flarum domain and download to PHP 7.4
After this change the web is online and if go to my forum setting I have: Flarum v1.2 with PHP 7.4

But in this point I testing and re-change one more time In Cpanel/ MultiPHP option I select my flarum domain and upload to PHP 8.0 . Then NOT send any command via terminal.
After this final change the web still alive (no have any ERROR 500) and if go to my forum setting I have: Flarum v1.2 with PHP 8.0.

Where is the problem?
Why with first flarum upgrade in PHP8 version I have ERROR 500 but if then download via Cpanel to 7.4 and re-update to 8.0 only via Cpanel all is working and in Admin said me stay in V8.0?

Data with comman: php flarum info

Flarum core 1.2.0
PHP version: 8.0.15
MySQL version: 5.5.5-10.2.41-MariaDB-cll-lve
Loaded extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, pcntl, readline, Reflection, SPL, session, standard, bcmath, bz2, calendar, ctype, curl, dba, dom, enchant, mbstring, fileinfo, ftp, gd, gettext, gmp, iconv, imap, intl, ldap, exif, mysqlnd, odbc, PDO, pgsql, Phar, posix,pspell, shmop, SimpleXML, snmp, soap, sockets, sqlite3, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, xml, xmlwriter, xsl, zip, mysqli, pdo_mysql, PDO_ODBC, pdo_pgsql, pdo_sqlite, xmlreader, sodium, mcrypt, pdo_sqlsrv, memcached, redis, imagick
+-----------------------------+---------+--------+
| Flarum Extensions           |         |        |
+-----------------------------+---------+--------+
| ID                          | Version | Commit |
+-----------------------------+---------+--------+
| flarum-markdown             | v1.2.0  |        |
| flarum-suspend              | v1.2.0  |        |
| flarum-flags                | v1.2.0  |        |
| matteocontrini-imgur-upload | v3.9.1  |        |
| fof-user-bio                | 1.0.2   |        |
| fof-terms                   | 1.1.2   |        |
| fof-share-social            | 1.0.1   |        |
| fof-pages                   | 1.0.1   |        |
| fof-oauth                   | 1.2.0   |        |
| fof-nightmode               | 1.2.0   |        |
| fof-merge-discussions       | 1.2.0   |        |
| fof-links                   | 1.0.3   |        |
| fof-ignore-users            | 1.0.2   |        |
| fof-formatting              | 1.0.2   |        |
| fof-cookie-consent          | 1.0.2   |        |
| flarum-tags                 | v1.2.0  |        |
| flarum-subscriptions        | v1.2.0  |        |
| flarum-sticky               | v1.2.0  |        |
| flarum-statistics           | v1.2.0  |        |
| flarum-mentions             | v1.2.0  |        |
| flarum-lock                 | v1.2.0  |        |
| flarum-likes                | v1.2.0  |        |
| flarum-lang-spanish         | 1.1.7   |        |
| flarum-emoji                | v1.2.0  |        |
| flarum-bbcode               | v1.2.0  |        |
| flarum-approval             | v1.2.0  |        |
+-----------------------------+---------+--------+

Walys

Now testing with php8.0 and if disable any extension have new ERROR 500 and need to downgrade to 7.4
And other problem view it that no working the personalized CSS I have in Flarum appearance

mmm...

clarkwinkelmann

Check log file in <flarum>/storage/logs for the full error message.

You can also enable debug in config.php temporarily to see errors directly on the web page.

Walys

clarkwinkelmann Thanks Clark
Review the files in /storage/logs/ and not view any news. The last modified data is 2021.
About enable debug in config.php change to "true" but not view any error directly in webpage.

luceos

Make sure to run composer update after switching php versions because composer installs stuff related to that. If you switch php versions after composer update the code installs might not be compatible with the new php version.

Walys

luceos Thanks Luceos.

Maybe this is the problem?
can also be caused by running composer with an older php binary from terminal?
When I install the first flarum version I do this with this command ea-php73 /opt/cpanel/composer/bin/composer to create-project flarum.

Now when I change to PHP 8.0 (ea-php80) in my Cpanel for the domain I have installed Flarum, then if run the composer update command in Terminal with normal code composer update all the webpage go with ERROR 500.

But now I go with one more test and run different with this command:
ea-php80 /opt/cpanel/composer/bin/composer update
And retesting my website and I think working ok with out problems.

A NOTE:
In my cpanel have the possibility to select PHP8.1 (alt-php81) for my domains.
IF change, then when run in terminal the same version with alt-php81 /opt/cpanel/composer/bin/composer update the system said me: bash: alt-php81: command not found

Maybe to run composer in PHP8.1 need other command address?

clarkwinkelmann

Walys if there is nothing in the Flarum log but the page still says 500 error then it's likely a webserver error page and not Flarum. You should find more details in the webserver log file. It could be an error parsing .htaccess file for example.

You should also be able to tell whether the error page is generated by Flarum or the webserver based on its look, Flarum 500 error is either a boot error and will show the word "Flarum", or for other Flarum 500 errors it's a centered text in the middle of the screen. Webserver errors are often just text aligned in top left, and sometimes mention the name and version of the webserver.

eSozluk

hello, go to php.ini section in cpanel and set the php memory limit to 512 mb from there, the problem will be resolved.