Blank page after nextcloud upgrade

Hi,

today I upgraded to 16.0.3 and it seemed like it worked like a charm as usually.
I was logged in after updating. Later I restarted apache because I changed memory_limit in php.ini to hopefully fix my initial problem. But after that restart I only get a blank page when I try to access nextcloud. All I found were issues after updating PHP but I didn’t do that so I’m a little bit desperate.

Thanks in advance.

Best regards

Nextcloud version: 16.0.3
Operating system and version : Ubuntu 16.04
Apache or nginx version: Apache/2.4.18 and nginx/1.14.2
PHP version: 7.3.7

Is this the first time you’ve seen this error?: Yes

The output of your Nextcloud log in Admin > Logging:

I cannot access Nextcloud

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

<?php
$CONFIG = array (
  'instanceid' => 'id',
  'passwordsalt' => 'secret',
  'secret' => 'victoria',
  'trusted_domains' =>
  array (
    0 => 'nextcloud.my.domain',
  ),
  'datadirectory' => '/opt/nextcloud/data',
  'overwrite.cli.url' => 'https://nextcloud.my.domain',
  'dbtype' => 'mysql',
  'version' => '16.0.3.0',
  'dbname' => 'db',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'admin',
  'dbpassword' => 'admin',
  'installed' => true,
  'maintenance' => false,
  'mail_smtpmode' => 'sendmail',
  'mail_smtpauthtype' => 'LOGIN',
  'mail_from_address' => 'my',
  'mail_domain' => 'adress',
  'mail_smtpsecure' => 'tls',
  'mail_smtphost' => 'smtp',
  'mail_smtpport' => '587',
  'theme' => '',
  'loglevel' => 2,
  'mail_smtpauth' => 1,
  'app_install_overwrite' =>
  array (
    0 => 'calendar',
  ),
  'filelocking.ttl' => 21600,
  'updater.secret' => 'secret',
);

The output of your Apache/nginx/system log in /var/log/____:

[Fri Jul 19 23:18:53.375283 2019] [mpm_prefork:notice] [pid 6371] AH00169: caught SIGTERM, shutting down
[Fri Jul 19 23:18:56.016602 2019] [ssl:warn] [pid 14189] AH01909: lists:443:0 server certificate does NOT include an ID which matches the server name
[Fri Jul 19 23:18:56.018841 2019] [:notice] [pid 14189] ModSecurity for Apache/2.9.2 (http://www.modsecurity.org/) configured.
[Fri Jul 19 23:18:56.018861 2019] [:notice] [pid 14189] ModSecurity: APR compiled version="1.5.2"; loaded version="1.5.2"
[Fri Jul 19 23:18:56.018877 2019] [:notice] [pid 14189] ModSecurity: PCRE compiled version="8.38 "; loaded version="8.38 2015-11-23"
[Fri Jul 19 23:18:56.018891 2019] [:notice] [pid 14189] ModSecurity: LUA compiled version="Lua 5.1"
[Fri Jul 19 23:18:56.018903 2019] [:notice] [pid 14189] ModSecurity: LIBXML compiled version="2.9.3"
[Fri Jul 19 23:18:56.018915 2019] [:notice] [pid 14189] ModSecurity: Original server signature: Apache
[Fri Jul 19 23:18:56.018926 2019] [:notice] [pid 14189] ModSecurity: Status engine is currently disabled, enable it by set SecStatusEngine to On.
[Fri Jul 19 23:18:56.020104 2019] [suexec:notice] [pid 14189] AH01232: suEXEC mechanism enabled (wrapper: /usr/lib/apache2/suexec)
[Fri Jul 19 23:18:57.027786 2019] [ssl:warn] [pid 14190] AH01909: lists:443:0 server certificate does NOT include an ID which matches the server name
[Fri Jul 19 23:18:57.040257 2019] [:error] [pid 14190] python_init: Python version mismatch, expected '2.7.6', found '2.7.12'.
[Fri Jul 19 23:18:57.040553 2019] [:error] [pid 14190] python_init: Python executable found '/usr/bin/python'.
[Fri Jul 19 23:18:57.040575 2019] [:error] [pid 14190] python_init: Python path being used '/usr/lib/python2.7/:/usr/lib/python2.7/plat-x86_64-linux-gnu:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload'.
[Fri Jul 19 23:18:57.040644 2019] [:notice] [pid 14190] mod_python: Creating 8 session mutexes based on 150 max processes and 0 max threads.
[Fri Jul 19 23:18:57.040661 2019] [:notice] [pid 14190] mod_python: using mutex_directory /tmp

After some time of research I found this post no-login-possible-white-page
which pointed me to https://securityheaders.com/ where I found out HTTP/1.1 was “500 Internal Server Error”.
I started looking for that and got to this site http-error-500-after-update-to-nc-13 with somebody suggesting to do

sudo -u www-data php occ upgrade

Doing so led to this:

~# /opt/plesk/php/7.3/bin/php occ upgrade
PHP Fatal error: Allowed memory size of 2097152 bytes exhausted (tried to allocate 4096 bytes) in /var/www/vhosts/my.domain/nextcloud.my.domain/3rdparty/composer/autoload_static.php on line 2098

Bringing me to this page allowed-memory-size-of…

I set memory_limit to “-1” and now I can access nextcloud again.
Strange thing is, I had already undone my previous change setting memory_limit to 16GB by setting value to 128MB which is the default.

Hopefully this will help someone sometime.

Best regards