Sudden "nextcloud is currently down"

[Sven-A]

NextCloudPi has been running on my Odroid HC2 for four years almost issue free. Now suddenly it appears than an automatic update broke something and I get this message in the browser when trying to access the Nextcloud WebUI:

This version of Nextcloud requires at least PHP 8.0
You are currently running 7.4.33. Please update your PHP version.

NCP-WebGUI is running but I SSH’d onto the server anyway and got this:

Running nc-info
Gathering information...
NextcloudPi version  v1.52.2
NextcloudPi image    NextCloudPi_11-27-20
OS                   Armbian 21.05.6 Buster \l . 4.14.222-odroidxu4 (armv7l)
automount            yes
USB devices          sda 
datadir              /media/USBdrive/ncdata
data in SD           no
data filesystem      btrfs
data disk usage      2,0T/3,7T
rootfs usage         4,2G/58G
swapfile             /var/swap
dbdir                /media/USBdrive/ncdatabase
Nextcloud check      error
HTTPD service        up
PHP service          up
MariaDB service      up
Redis service        up
HPB service          down
Postfix service      up
Internet check       ok
Public IPv4          178.x.x.x
Public IPv6          not found
Port 80              closed
Port 443             closed
IP                   192.168.2.32
Gateway              192.168.2.1
Interface            enx001e063656f8
Certificates         none
NAT loopback         no
Uptime               13:14

When trying to manually update Nextcloud to any version (either latest or 25.0.6 following this suggestion) it aborts with: nextcloud is currently down. Updating (the already current) NCP has no effect on that issue.

I was willing to take the arduous but safe approach of a complete re-install. But unfortunately I can’t even get a fresh backup for that purpose. Similar message:

Running nc-backup
Installing template 'ncp-metrics.cfg.sh'...
Cannot load Zend OPcache - it was already loaded
Cannot load Zend OPcache - it was already loaded
check free space...
Cannot load Zend OPcache - it was already loaded
Cannot load Zend OPcache - it was already loaded
This version of Nextcloud requires at least PHP 8.0<br/>You are currently running 7.4.33. Please update your PHP version.Abort...
Cannot load Zend OPcache - it was already loaded
This version of Nextcloud requires at least PHP 8.0<br/>You are currently running 7.4.33. Please update your PHP version.Cannot load Zend OPcache - it was already loaded
This version of Nextcloud requires at least PHP 8.0<br/>You are currently running 7.4.33. Please update your PHP version.Done. Press any key...

With my limited skills I tried manually updating PHP. But after several futile attempts, that completely broke apache, I was happy to safely restore the described state.

Please, is there any way to at least obtain a fresh backup? I am not expecting an easy solution to the actual problem, but am open to any positive surprise

The logs are of little help:

/var/log/apache2/error.log
[Wed Jul 26 22:40:18.764670 2023] [ssl:error] [pid 8828:tid 3069295200] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: CN=localhost / issuer: CN=localhost / serial: xxx>
[Wed Jul 26 22:40:18.764703 2023] [ssl:error] [pid 8828:tid 3069295200] AH02604: Unable to configure certificate localhost:4443:0 for stapling
[Wed Jul 26 22:40:18.787830 2023] [ssl:error] [pid 8829:tid 3069295200] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: CN=localhost / issuer: CN=localhost / serial: xxx>
[Wed Jul 26 22:40:18.787857 2023] [ssl:error] [pid 8829:tid 3069295200] AH02604: Unable to configure certificate localhost:4443:0 for stapling
[Wed Jul 26 22:40:18.793462 2023] [mpm_event:notice] [pid 8829:tid 3069295200] AH00489: Apache/2.4.56 (Debian) OpenSSL/1.1.1n configured -- resuming normal operations
[Wed Jul 26 22:40:18.793558 2023] [core:notice] [pid 8829:tid 3069295200] AH00094: Command line: '/usr/sbin/apache2'

log/apache2/nc-error.log
[Wed Jul 26 22:40:18.763197 2023] [ssl:error] [pid 8828:tid 3069295200] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: CN=localhost / issuer: CN=localhost / serial: xxx>
[Wed Jul 26 22:40:18.763333 2023] [ssl:error] [pid 8828:tid 3069295200] AH02604: Unable to configure certificate localhost:443:0 for stapling
[Wed Jul 26 22:40:18.786631 2023] [ssl:error] [pid 8829:tid 3069295200] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: CN=localhost / issuer: CN=localhost / serial: xxx>
[Wed Jul 26 22:40:18.786675 2023] [ssl:error] [pid 8829:tid 3069295200] AH02604: Unable to configure certificate localhost:443:0 for stapling

[tflidd]

@Sven-A

Please, is there any way to at least obtain a fresh backup?

You have to do a backup before you start changing things. You can backup the current state…

Regarding updating your system or php, there are a few topics here. I didn’t go through them all to see which applies the best (and probably I missed a few on the way):

»This version of Nextcloud is not compatible with > PHP 8.0.« using nextcloudpi

I had a running installation for about a year. The usb-stick with the file system broke. I made a new install of debian bullseye on a raspberry pi 4. Then I installed nextcloud using this one-stop-solution from here: https://raw.githubusercontent.com/nextcloud/nextcloudpi/master/install.sh That worked, Nextcloud was running, I could log in as ncp (»:4443«). Then I tried to restore my backup, but it doesn’t run, because obviously the installation of nextcloud via this install script brought ph…

Several issues with NCP update and PHP update

Debian 11 Stable on a x64 NUC Nextcloud 24.0.5.1 NextCloudPi version v1.50.3 PHP 7.4.30 Major issue, PHP 8.1 Oct. 22nd I ran a package update on my Debian 11 server and it updated the PHP version to 8.1x. After this I was unable to access the webUI for Nextcloud, and Webdav wouldn’t communicate. I rolled it back with a snapshot to undo the package updates, and it all works again. I read here [SOLVED] After Debian 11 upgrade "Failed to connect to the database..." that Nextcloud doesn’t sup…

What upgrade first - NextCloudPi (from v1.52.1 to v1.52.2) or PHP (from 7.4.33 to 8.0)

Ok, so here we are: I rolled back a backup: – With sudo mc I started the midnight commander and changed the latest backup file to r/w for everyone (chmod). – By using mc I copied the backup file from my not supported USB drive to the SD card into the path /home/pi/ (seems to be the right fs). – I restored to a running NC instance (sudo nc-config) from the backup file to prevent unexpacted side effects while updating NC later. I updated php from 7.4 to 8.0 using this and this tutorial: – Th…

I have latest NextCloudPi version, but dated PHP version

Nextcloud version: 25.0.1.1 Operating system and version: Debian GNU/Linux 11. 5.15.32-v8+ (aarch64) Apache or nginx version: Apache/2.4.56 (Debian) PHP version (eg, 7.4): PHP 7.4.33 The issue you are facing: I’m running NextCloudPi v1.52.0. When I go to update to Nextcloud 26, using the NCP admin I get this message: [ nc-update-nextcloud ] (Thu May 11 21:25:57 BST 2023) We need to upgrade PHP. This process cannot be performed from the web UI. Please use 'ncp-config' from the terminal (v…

PHP 7.4 to 8.0 to support upgrade NC25 to NC26 on NextcloudPi, server down

I was almost hit by first Murphy’s rule : Never try to fix something working ! I made a backup and export my NCP setting. I wrote a new NCP image (1.52 + NC26 and PHP8). I restored my backup and import my settings. (logically went back to NC25 but with PHP8.0) => the path to my datas was not restored, my Let’s encrypt was not working (couldn’t write registered adress file). As I only have one MicroSD card I have to joggle between images. At the end, I restored my NC25/PHP7.4 image and got …

[Sven-A]

Thank you. But since i had no success randomly trying the solution to other peoples problems I took the arduous approach, installed a clean Armbian Bullseye, used the NPC-curl-Installer, manually recreated all user accounts and coppied an rescanned their files.

Now I am still trying to rescue my family calendar from the remains of the old database, to feed them into Calcardbackup, but that is a minor issue.

My mistake was, that I had tried too hard last winter to update my system using an image, that other users already had complained about. That went a bit dodgy and I was on borrowed time from then onwards. Since I can hardly expect the NCP maintainers to keep current images for all kinds of exotic SBCs of the last decade, I have learned my lesson: Stick to the Armbian guys for best HW support and current OS and then add NCP on top.

UPDATE: Also I learned to keep the automatic NCP- and NC-updates deactivated and apply those manually after a fresh backup and some research about common issues.