Nc-update-next-cloud from 20.0.4.0 fail with Error downloading

Nextcloudpi on docker container on rpi 4 8gb

Nextcloud version (eg, 20.0.5): 20.0.4.0
Operating system and version (eg, Ubuntu 20.04): Debian GNU/Linux 10. 5.10.63-v7l+ (armv7l)
Apache or nginx version (eg, Apache 2.4.25): 2.4.38
PHP version (eg, 7.4): 7.3

The issue you are facing:
When trying to update nexcloud from nextcloudpi web ui using nc-update-next-cloud I’m getting:

[ nc-update-nextcloud ] (Fri Oct 15 05:52:14 UTC 2021)
Current   Nextcloud version 20.0.4.0
Available Nextcloud version 21.0.4
Download Nextcloud 21.0.4...
Error downloading
Clean up...

ncp system info:


NextCloudPi version	v1.40.10
NextCloudPi image	NextCloudPi_docker_01-19-21
OS	Debian GNU/Linux 10. 5.10.63-v7l+ (armv7l)
automount	no
USB devices	sda
datadir	/data/nextcloud/data
data in SD	no
data filesystem	ext2/ext3
data disk usage	5.1G/3.6T
rootfs usage	15G/59G
swapfile	/var/swap
dbdir	/data/database
Nextcloud check	ok
Nextcloud version	20.0.4.0
HTTPD service	up
PHP service	up
MariaDB service	up
Redis service	up
HPB service	down
Postfix service	up
internet check	ok
port check 80	closed
port check 443	closed
IP	
gateway	
interface	eth0
certificates	
NAT loopback	no
uptime	1day

The output of your Nextcloud log in Admin > Logging:
Nothing in the logs from the time of the update request

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

root@XXX:/# cat /data/nextcloud/config/config.php
<?php
$CONFIG = array (
  'passwordsalt' => 
  'secret' =>
  'trusted_domains' => 
  array (
    0 => 'localhost',
    5 => 'nextcloudpi.local',
    7 => 'nextcloudpi',
    8 => 'nextcloudpi.lan',
    1 => '',
    6 => '',
    20 => '',
    21 => '',
    12 => '',
  ),
  'datadirectory' => '/data/nextcloud/data',
  'dbtype' => 'mysql',
  'version' => '20.0.4.0',
  'overwrite.cli.url' => '',
  'dbname' => 'nextcloud',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'ncadmin',
  'dbpassword' => '',
  'installed' => true,
  'instanceid' => 'ocg8w7gexsjy',
  'memcache.local' => '\\OC\\Memcache\\Redis',
  'memcache.locking' => '\\OC\\Memcache\\Redis',
  'redis' => 
  array (
    'host' => '/var/run/redis/redis.sock',
    'port' => 0,
    'timeout' => 0.0,
    'password' => '',
  ),
  'tempdirectory' => '/var/www/nextcloud/data/tmp',
  'mail_smtpmode' => 'sendmail',
  'mail_smtpauthtype' => 'LOGIN',
  'mail_from_address' => 'admin',
  'mail_domain' => 'ownyourbits.com',
  'preview_max_x' => '2048',
  'preview_max_y' => '2048',
  'jpeg_quality' => '60',
  'overwriteprotocol' => 'https',
  'maintenance' => false,
  'loglevel' => 2,
);

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

Apache2/error.log

[Fri Oct 15 05:48:55.061689 2021] [authz_host:error] [pid 7188:tid 3008246816] [client 192.168.68.106:52668] AH01753: access check of 'localhost' to /ncp-launcher.php failed, reason: unable to get the remote host name

Apache2/other_vhosts_access.log

localhost:4443 192.168.68.106 - - [15/Oct/2021:05:48:55 +0000] "POST /ncp-launcher.php HTTP/2.0" 200 181 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0"

You can not run 64bits software on 32bit hardware, afaik.

see 64bit - is my linux ARM 32 or 64 bit? - Unix & Linux Stack Exchange

Weird tho, I thought all rpi4 were 64bit, but apparently not.

pi@raspberrypi:~ $ lscpu
Architecture:        armv7l
Byte Order:          Little Endian
CPU(s):              4
On-line CPU(s) list: 0-3
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):           1
Vendor ID:           ARM
Model:               3
Model name:          Cortex-A72
Stepping:            r0p3
CPU max MHz:         2200.0000
CPU min MHz:         600.0000
BogoMIPS:            108.00
Flags:               half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32

AFAIK Cortex-A72 is a 64bit, but according to https://forums.raspberrypi.com/viewtopic.php?t=245846 it’s due to the OS (Raspbian)

Anyway how can I proceed?

Wait, I’m confused… aren’t you supposed to update docker containers by pulling the new image?

docker run -d -p 4443:4443 -p 443:443 -p 80:80 -v /PATH/TO/YOUR/NCDATA:/data –name nextcloudpi ownyourbits/nextcloudpi YOUR.DOMAIN

https://docs.nextcloudpi.com/en/how-to-get-started-with-ncp-docker/

I’m still getting started with docker, but afaik docker containers are non persistant, meaning, if you manage to update from within, at the next reboot you would be back to the original.

Or do I get something wrong?

AFAIK Cortex-A72 is a 64bit, but according to Raspberry pi 4 shows armv7l at lscpu command? - Raspberry Pi Forums it’s due to the OS (Raspbian

wait a sec…
yes the Pi has a 64bit processor… but as @OliverV wrote, you are running a 32bit os

i think lscpu should give you a output on what you run and what the processor is.
and in your case it’s a

armv71 OS
running on a
armv72 hardware

Make sure you have a 64bit OS installed and pull the latest image,
Or download and burn the latest image.

Please start your own thread.

@OliverV ok, let me re state this:

I’m quite sure… :sweat_smile:
…not confused.

Thanks for your responses! I’ll install a 64 os and keep you posted

1 Like

Just don’t install Ubuntu 21.10 yet, it just came out days ago and docker is not yet ready, at least not straightforward.

(I’m saying that because I just did, and I don’t have physical access to my pi… so I have to wait… haha)

I just tried on my non-production Pi4 running Ubuntu 20.04 (64bit)
if I use the Docker run command:

docker run -d -p 4443:4443 -p 443:443 -p 80:80 -v /home/ubuntu/docker/ncdata:/data --name nextcloudpi ownyourbits/nextcloudpi 192.168.0.14

I get NC 20 and there is no way to update. Neither from within the docker container nor by pulling nextcloudpi ownyourbits/nextcloudpi:latest

So I added -arm64 to the run command:

docker run -d -p 4443:4443 -p 443:443 -p 80:80 -v /home/ubuntu/docker/ncdata64:/data --name nextcloudpi64 ownyourbits/nextcloudpi-arm64 192.168.0.14

and there you go, I’m on 21.0.4.1


So, my theory is that the standard docker run command that can be found on ownyourbits, does not detect the Ubuntu 64bit system. So, it installs the 32bit version. That version, however, will not be updated to NC 21 anymore.

After installing Ubuntu 20.04 64 bit, I can get NC 21 as suggested above, but only if I’m not mounting the existing data path. If I’m using the same data path it’s still stuck on 20.0.4 and getting the same error when trying to update.

Same issue with backup: Once I restore from backup, it goes back to 20.0.4 and fail to upgrade.

Is there a way to keep\restore the data and being able to upgrade the NC version at the same time?

Thx!

Hi, i have the same error but native on a Raspi3, no docker.
Could this be the same problem with having raspbian in 32bit installed?

lscpu gives me the following:

Architecture:        armv7l
Byte Order:          Little Endian
CPU(s):              4
On-line CPU(s) list: 0-3
Thread(s) per core:  1
Core(s) per socket:  4
Socket(s):           1
Vendor ID:           ARM
Model:               4
Model name:          Cortex-A53
Stepping:            r0p4
CPU max MHz:         1400.0000
CPU min MHz:         600.0000
BogoMIPS:            38.40
Flags:               half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm
 crc32

thx