Nextcloud 25 update broke my instance

[nextcloudpiuser]

Nextcloud version (eg, 20.0.5): 25.0.0
Operating system and version (eg, Ubuntu 20.04): Distributor ID: Raspbian Description: Raspbian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye
Apache or nginx version (eg, Apache 2.4.25): Apache/2.4.53 (Raspbian)
PHP version (eg, 7.4): 7.4.28 (cli)

The issue you are facing:

Today I went in and updated to version 25 of Nextcloud. Update seemed to go fine. At the end I clicked the two buttons as usual. Disable maintence mode and then proceed to the frontend. Once I clicked that last button I was redirected and now it just shows a blank page. Desktop app and mobile apps can no longer connect.

Seems the update completely broke my instance. Any insight to help would be greatly appreciated! Thank you in advance.

Is this the first time you’ve seen this error? (Y/N): Y

Steps to replicate it:

1. Update nextcloud from version 24 to 25
2. Nothing works now

The output of your Nextcloud log in Admin > Logging:

Can't access this as I can't login

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

<?php
$CONFIG = array (
  'passwordsalt' => 'xxxxxx',
  'secret' => 'xxxxxxx',
  'trusted_domains' => 
  array (
    0 => 'localhost',
    5 => 'nextcloudpi.local',
    7 => 'nextcloudpi',
    8 => 'nextcloudpi.lan',
    11 => '23.226.128.19',
    1 => '192.168.1.101',
    3 => 'localhost',
    20 => 'mycloud.com',
    14 => 'nextcloudpi',
  ),
  'datadirectory' => '/media/myCloudDrive/ncdata',
  'dbtype' => 'mysql',
  'version' => '24.0.6.1',
  'overwrite.cli.url' => 'https://localhost/',
  'dbname' => 'nextcloud',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'ncadmin',
  'dbpassword' => 'raspberry',
  'installed' => true,
  'instanceid' => 'ochvelgsn5v1',
  'memcache.local' => '\\OC\\Memcache\\Redis',
  'memcache.locking' => '\\OC\\Memcache\\Redis',
  'redis' => 
  array (
    'host' => '/var/run/redis/redis.sock',
    'port' => 0,
    'timeout' => 0.0,
    'password' => 'xxx',
  ),
  'tempdirectory' => '/media/myCloudDrive/ncdata/tmp',
  'mail_smtpmode' => 'smtp',
  'mail_smtpauthtype' => 'LOGIN',
  'mail_from_address' => 'xxx',
  'mail_domain' => 'xxx',
  'preview_max_x' => '2048',
  'preview_max_y' => '2048',
  'jpeg_quality' => '60',
  'overwriteprotocol' => 'https',
  'maintenance' => false,
  'logfile' => '/media/myCloudDrive/ncdata/nextcloud.log',
  'mail_sendmailmode' => 'smtp',
  'mail_smtpauth' => 1,
  'mail_smtphost' => 'xxx',
  'mail_smtpport' => '465',
  'mail_smtpsecure' => 'ssl',
  'mail_smtpname' => 'xxx',
  'mail_smtppassword' => 'xxx',
  'htaccess.RewriteBase' => '/',
    'htaccess.RewriteBase' => '/',
  'theme' => '',
  'loglevel' => 2,
  'updater.release.channel' => 'stable',
  'updater.secret' => 'xxx',
);

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

Oct 20 14:08:58 nextcloudpi systemd[1]: notify_push.service: Main process exited, code=exited, status=203/EXEC
Oct 20 14:08:58 nextcloudpi systemd[1]: notify_push.service: Failed with result 'exit-code'.
Oct 20 14:09:01 nextcloudpi CRON[2614]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Oct 20 14:09:03 nextcloudpi systemd[1]: Starting Clean php session files...
Oct 20 14:09:03 nextcloudpi systemd[1]: phpsessionclean.service: Succeeded.
Oct 20 14:09:03 nextcloudpi systemd[1]: Finished Clean php session files.
Oct 20 14:09:18 nextcloudpi systemd[1]: notify_push.service: Scheduled restart job, restart counter is at 82.
Oct 20 14:09:18 nextcloudpi systemd[1]: Stopped Push daemon for Nextcloud clients.
Oct 20 14:09:18 nextcloudpi systemd[1]: Started Push daemon for Nextcloud clients.
Oct 20 14:09:18 nextcloudpi systemd[2679]: notify_push.service: Failed to locate executable /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:09:18 nextcloudpi systemd[2679]: notify_push.service: Failed at step EXEC spawning /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:09:18 nextcloudpi systemd[1]: notify_push.service: Main process exited, code=exited, status=203/EXEC
Oct 20 14:09:18 nextcloudpi systemd[1]: notify_push.service: Failed with result 'exit-code'.
Oct 20 14:09:38 nextcloudpi systemd[1]: notify_push.service: Scheduled restart job, restart counter is at 83.
Oct 20 14:09:38 nextcloudpi systemd[1]: Stopped Push daemon for Nextcloud clients.
Oct 20 14:09:38 nextcloudpi systemd[1]: Started Push daemon for Nextcloud clients.
Oct 20 14:09:38 nextcloudpi systemd[2681]: notify_push.service: Failed to locate executable /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:09:38 nextcloudpi systemd[2681]: notify_push.service: Failed at step EXEC spawning /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:09:38 nextcloudpi systemd[1]: notify_push.service: Main process exited, code=exited, status=203/EXEC
Oct 20 14:09:38 nextcloudpi systemd[1]: notify_push.service: Failed with result 'exit-code'.

Oct 20 14:09:38 nextcloudpi systemd[1]: Stopped Push daemon for Nextcloud clients.
Oct 20 14:09:38 nextcloudpi systemd[1]: Started Push daemon for Nextcloud clients.
Oct 20 14:09:38 nextcloudpi systemd[2681]: notify_push.service: Failed to locate executable /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:09:38 nextcloudpi systemd[2681]: notify_push.service: Failed at step EXEC spawning /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:09:38 nextcloudpi systemd[1]: notify_push.service: Main process exited, code=exited, status=203/EXEC
Oct 20 14:09:38 nextcloudpi systemd[1]: notify_push.service: Failed with result 'exit-code'.
Oct 20 14:09:58 nextcloudpi systemd[1]: notify_push.service: Scheduled restart job, restart counter is at 84.
Oct 20 14:09:58 nextcloudpi systemd[1]: Stopped Push daemon for Nextcloud clients.
Oct 20 14:09:58 nextcloudpi systemd[1]: Started Push daemon for Nextcloud clients.
Oct 20 14:09:58 nextcloudpi systemd[2682]: notify_push.service: Failed to locate executable /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:09:58 nextcloudpi systemd[2682]: notify_push.service: Failed at step EXEC spawning /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:09:58 nextcloudpi systemd[1]: notify_push.service: Main process exited, code=exited, status=203/EXEC
Oct 20 14:09:58 nextcloudpi systemd[1]: notify_push.service: Failed with result 'exit-code'.
Oct 20 14:10:02 nextcloudpi CRON[2688]: (www-data) CMD (php -f /var/www/nextcloud/cron.php)
Oct 20 14:10:19 nextcloudpi systemd[1]: notify_push.service: Scheduled restart job, restart counter is at 85.
Oct 20 14:10:19 nextcloudpi systemd[1]: Stopped Push daemon for Nextcloud clients.
Oct 20 14:10:19 nextcloudpi systemd[1]: Started Push daemon for Nextcloud clients.
Oct 20 14:10:19 nextcloudpi systemd[2690]: notify_push.service: Failed to locate executable /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:10:19 nextcloudpi systemd[2690]: notify_push.service: Failed at step EXEC spawning /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:10:19 nextcloudpi systemd[1]: notify_push.service: Main process exited, code=exited, status=203/EXEC
Oct 20 14:10:19 nextcloudpi systemd[1]: notify_push.service: Failed with result 'exit-code'.
Oct 20 14:10:39 nextcloudpi systemd[1]: notify_push.service: Scheduled restart job, restart counter is at 86.
Oct 20 14:10:39 nextcloudpi systemd[1]: Stopped Push daemon for Nextcloud clients.
Oct 20 14:10:39 nextcloudpi systemd[1]: Started Push daemon for Nextcloud clients.
Oct 20 14:10:39 nextcloudpi systemd[2691]: notify_push.service: Failed to locate executable /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:10:39 nextcloudpi systemd[2691]: notify_push.service: Failed at step EXEC spawning /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:10:39 nextcloudpi systemd[1]: notify_push.service: Main process exited, code=exited, status=203/EXEC
Oct 20 14:10:39 nextcloudpi systemd[1]: notify_push.service: Failed with result 'exit-code'.
Oct 20 14:10:59 nextcloudpi systemd[1]: notify_push.service: Scheduled restart job, restart counter is at 87.
Oct 20 14:10:59 nextcloudpi systemd[1]: Stopped Push daemon for Nextcloud clients.
Oct 20 14:10:59 nextcloudpi systemd[1]: Started Push daemon for Nextcloud clients.
Oct 20 14:10:59 nextcloudpi systemd[2692]: notify_push.service: Failed to locate executable /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:10:59 nextcloudpi systemd[2692]: notify_push.service: Failed at step EXEC spawning /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:10:59 nextcloudpi systemd[1]: notify_push.service: Main process exited, code=exited, status=203/EXEC
Oct 20 14:10:59 nextcloudpi systemd[1]: notify_push.service: Failed with result 'exit-code'.
Oct 20 14:11:03 nextcloudpi systemd[1]: Starting Collect apt metrics for prometheus-node-exporter...
Oct 20 14:11:03 nextcloudpi systemd[1]: Starting Collect SMART metrics for prometheus-node-exporter...
Oct 20 14:11:04 nextcloudpi systemd[1]: prometheus-node-exporter-smartmon.service: Succeeded.
Oct 20 14:11:04 nextcloudpi systemd[1]: Finished Collect SMART metrics for prometheus-node-exporter.
Oct 20 14:11:13 nextcloudpi systemd[1]: prometheus-node-exporter-apt.service: Succeeded.
Oct 20 14:11:13 nextcloudpi systemd[1]: Finished Collect apt metrics for prometheus-node-exporter.
Oct 20 14:11:13 nextcloudpi systemd[1]: prometheus-node-exporter-apt.service: Consumed 9.781s CPU time.
Oct 20 14:11:19 nextcloudpi systemd[1]: notify_push.service: Scheduled restart job, restart counter is at 88.
Oct 20 14:11:19 nextcloudpi systemd[1]: Stopped Push daemon for Nextcloud clients.
Oct 20 14:11:19 nextcloudpi systemd[1]: Started Push daemon for Nextcloud clients.
Oct 20 14:11:19 nextcloudpi systemd[2748]: notify_push.service: Failed to locate executable /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:11:19 nextcloudpi systemd[2748]: notify_push.service: Failed at step EXEC spawning /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:11:19 nextcloudpi systemd[1]: notify_push.service: Main process exited, code=exited, status=203/EXEC
Oct 20 14:11:19 nextcloudpi systemd[1]: notify_push.service: Failed with result 'exit-code'.
Oct 20 14:11:40 nextcloudpi systemd[1]: notify_push.service: Scheduled restart job, restart counter is at 89.
Oct 20 14:11:40 nextcloudpi systemd[1]: Stopped Push daemon for Nextcloud clients.
Oct 20 14:11:40 nextcloudpi systemd[1]: Started Push daemon for Nextcloud clients.
Oct 20 14:11:40 nextcloudpi systemd[2749]: notify_push.service: Failed to locate executable /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:11:40 nextcloudpi systemd[2749]: notify_push.service: Failed at step EXEC spawning /var/www/nextcloud/apps/notify_push/bin/armv7/notify_push: No such file or directory
Oct 20 14:11:40 nextcloudpi systemd[1]: notify_push.service: Main process exited, code=exited, status=203/EXEC
Oct 20 14:11:40 nextcloudpi systemd[1]: notify_push.service: Failed with result 'exit-code'.

PASTE HERE

Output errors in nextcloud.log in /var/www/ or as admin user in top right menu, filtering for errors. Use a pastebin service if necessary.

not seeing any errors in this file

[ZendaiOwl]

It says ARMv7 (i.e 32bit)

Nextcloud doesn’t have support for 32bit anymore in version 25 and isn’t usable on a 32bit system beyond version 24

32-bit support ends with Nextcloud 24, which reachs EOL 05/2023

According to Maintenance and Release schedule Nextcloud 24 will be supported until 05/2023. This means 32-bit systems might continue to receive updates through May, but think of this as… Nextcloud 24 will be supported with bug fixes through May of 2023 Time to Change Architectures This is not surprising news, 32-bit support was already discontinued, but now it will not work at all as of Nextcloud 25. Nextcloud 25 requires 64-bit systems The requirement of 64-bit is now in the official do…

Edit: Here’s another topic about this

"It seems like you are running a 32-bit PHP version. Nextcloud needs 64-bit to run well. Please upgrade your OS and PHP to 64-bit!

I pressed upgrade… your thing said “Hey all good…” it progressed to upgrade me… but then failed in a big way, i later found on the foums that 25 only supports x64 ? why didn’t the prechecks find this and warn me? (restored back to 24.0.6 as i had an image so no problems) but really… you need to warn users

[REAPERSbattlecry]

And I’m pretty sure that NC25 doesn’t work with php7.4

https://docs.nextcloud.com/server/latest/admin_manual/installation/system_requirements.html

[szaimen]

NC25 indeed still works with PHP7.4

[irongate]

I second this post…

Upgraded to latest stable version and got a bunch of errors.

Eventually, I just deleted the entire old instance and started from scratch.

Installation went fine, but now on a new instance, occ doesn’t run anymore.

I get this error:

TypeError: json_decode(): Argument #1 ($json) must be of type string, bool given in nextcloud/lib/private/IntegrityCheck/Checker.php:443

I thought it might be the php version issue. So, I deleted everything AGAIN… and installed php 8.1… and downloaded the latest nextcloud tar.

I still get this error.

As a side note, the updater should have indicated that 64bit OS was needed and refused to update. That would have been nice. It also should have warned… in big bold letters… about Deprecating PHP 7.4…

All in all, the auto upgrade process and pathway to 25 has been a disaster for my server.

---

EDIT:

And, I’m really not happy with the giant Error Warning about push notifications. I don’t use push notifications, can I remove the Giant Error Warning signs?

---

EDIT2:

My json_decode error seems to have been related to a few 32 libraries hanging around on my system after switching from 32bit to 64bit libraries. The TURN server needed to be reconfigured as well.

Now everything seems to be working fine.

It’s definitely important to warn people of something as large a problem as 32bit vs. 64bit and refuse to upgrade. Legacy installs from 5 or 6 years ago on OSes that have been running nearly a decade can be difficult to switch.

The good news is, my install is now all set for the 2038 problem.