Fresh NC install of 11.0.1 (stable) on R.Pi 3 using ArchARM, postgres and apache. Everything seemed to go OK, except I’m getting an error about a code integrity check and clicking on the List of invalid files link tells me the problem is in the hash for .user.ini:
[expected] => 467d4f028c447895716a2b7859ed6e569f8ee34b87b51d73dab2e6a9ca4fbe63172c7be3e365ae864a60408286afcce852dd38ee544b61685ed4ee5e021fecb0
[current] => cf83e1357eefb8bdf1542850d66d8007d620e4050b5715dc83f4a921d36ce9ce47d0d13c5d85f2b0ff8318d2877eec2f63b931bd47417a81a538327af927da3e
I’ve had a look around to solve this myself and can report:
I ssh’d into the Pi to download the NC tar, extracted all content to the alarm user (<== standard normal user created by ArchARM install) homedir and then mv’d it to web root ~ so a) it’s not a missing .user.ini and b) I don’t think it’s a binary|ascii ftp problem which seem to be the main reasons for this error.
I haven’t changed any of the settings in the .user.ini file, so it’s not a case of my changes messing with the hash.
When I saw the error, I downloaded a fresh NC bzip file, extracted it and mv’d just the .user.ini file to webroot/nextcloud and got the same hash errors (expected and current both the same).
[alarm@alarm ~]$ sudo cat /srv/http/nextcloud/.user.ini
Apart from that, I’m stuck. Is there anything else I can post to help with solving this?
PS: I don’t know if it makes any difference, but I’m not using https yet - thought I’d get it working locally first on just http.