NOBL

I finally successfully updated Nextcloud to version 31.0.10 on my Odroid N2+ 😅 Despite all official information, an update is possible on a system running nextcloud installed via the script ! It is not necessary to buy a new hardware just to run nextcloud on your Armbian SBC in order to get the update. I did the following: Updated nextcloudpi to version 1.55.4 which was never released but just tagged on github Nextcloudpi tagged page on github via the ncp-config menu system (Updates/nc-update) Updated nextcloud to version 31.0.10, again, via the menu system (Updates/nc-update-nextcloud version 31.0.10) I don't really know why this information is not readily available on the nextcloudpi github page nor anywhere else I looked. Have fun Norbert

Thanks for your post ! I have checked the source code for 1.55.4 and, indeed, it shows "nextcloud_version": "31.0.2", in etc/ncp.cfg file. That probably means, an update of nextcloud to 31.0.2 resp. 31.0.10 (the current version) would be possible. It is consistent with the update method you did. The nightly automatic backup to an external disk works fine. I have installed 1.55.4 on my nextcloud system. I'll do another backup I'll try to update nextcloud to 30.0.10 using 1.55.4 tomorrow. I'll report the result over here and mark it as solution, if successful. I simply wonder why any information of this possible update method was not mentioned anywhere - perhaps except on matrix. Joining matrix chat is on my to-do list, anyway. Thanks to eselarm for the hint for quoting a previous post 😀 Kind regards Norbert

Hi eselarm Thank you for your post. I can't still find a button to answer directly to your post in this forum. If I replace the HW - and I could afford it - then the question of migration to the new platform arises. Nextcloudpi worked fine on armbian releases, there is no point in changing the OS. Obviously it is close enough to debian so the "port" from debian to armbian is not very difficult. As long as the same base version (bookworm, trixie) is used. Even debian 12 did not support the required PHP version 8.1 at the time, nextcloud required it. But nextcloudpi still did the update to that nextcloud version with the result of nextcloud not running. I host nextcloud at home and I don't want a fan running at full speed in my living room. The "generic x86-64" (or amd64) is really no choice. Once I bought a WLAN router with built-in room for a disk but even with no disk installed the fan did run and couldn't be stopped. Returned it. I heared about proxmox, docker. LXC and LXD. For the latter there are images for x86-64 HW with nextcloudpi provided. But choosing the right HW and do the migration to it seems difficult to me. Regards Norbert

Hi geoW Couldn't find any button to reply to your answer to my question in this forum 😐 . But here it goes: I know well how to do updates of armbian, nextcloud and nextcloudpi and how to use ncp-config. I configured it even to do the updates automatically but was burned twice - once with Armbian OS (didn't boot because of compressed kernel modules) and once with nextcloudpi updates to nextcloud without prior checking the required PHP version (8.1). So, no automatic updates any more, but manual checks, of course. I have configured an RSS feed to the nextcloudpi github page. That didn't include the never officially released version 1.55.4 of nextcloudpi, of course. In the release notes for nextcloudpi (v1.55.3) it mentions support for nextcloud 30. See the github page: Nextcloud 30.0.1 (can be automatically updated to latest minor version) PHP 8.3 Debian bookworm Armbian v24.08 Fine. There are no release notes for version v1.55.4 nor where this one officially released, at all, just tagged. So, where do you get the information that an update to nextcloud version 31 is supported by this version of nextcloudpi (v.1.55.4) ? Did you successfully update nextcloud to version 31.x with this version v1.55.4 of nextcloudpi ? Where do you get the information about someone working to allow updates to nextcloud version 32 via nextcloudpi ? Unless there is an official report about this, I won't simply update my installation. So, my original question is: what to do after the end of support for version 30.0.x ? Added: OK, I see: you are running one of the provided images for your Raspi5. I don't have a Raspi 4 or 5, That's why I posted my problem in this forum. So the story is: There is no support for any HW except for the images provided. I agree, that Nextcloud GmbH is overflowed with european requests for offers and work due to the politics of the orange head in the US. This is favourable in my opinion. So, my impression is that, obviously, nobody cares about the few nextcloudpi users not running nextcloud on HW other than on the images provided. Regards Norbert

Hi Unfortunately, I use an Odroid N2 (and N2+) for nextcloud installed via the nextcloudpi script. Now, the support is gone and there are no longer updates for nextcloud beyond version 30.0.x available. Currently I am running nextcloud 30.0.17. The version 30.0.x will reach end-of-support soon. I can imagine the following alternatives: Use armbian-config to install nextcloud - but will it do the update correctly or at all esp. for my external disks which nextcloud is using ? Use the image for the Odroid C2 (another arm-based SBC) and replace the kernel by the one for the Odroid N2+ Port the script from the Odroid C2 image to my Odroid N2 Buy an Raspi 4 or, even better, a Raspi 5 and use the images for that HW - how about a migration path ? So what do you suggest ? I think I could do all of those alternatives myself and I have an Odroid N2 and an Odroid N2+ useable for testing purposes. One of those was planned to run HomeAssistant and I'm happy that HAOS is supported on my hardware. But that can be postponed to later. Kind regards Norbert Edit: Added question for the migration path if HW changed to Raspi 4 or 5

I tried to use strace to determine the cause of this message but couldn't find it. There are really some config files in /etc missing but adding them did not resolve the issue.

This messge shows up on the xfce edition Armbian_25.2.1_Uefi-arm64_bookworm_current_6.12.13_xfce_desktop.ing.xz as well as for the cinnamon edition: Armbian_25.2.1_Uefi-arm64_bookworm_current_6.12.13_cinnamon-backported-mesa_desktop.img.xz

Solved it by using the XFCE Armbian_25.2.1_Uefi-arm64_bookworm_current_6.12.13_xfce_desktop.img.xz instead of the cinnamon Armbian_25.2.1_Uefi-arm64_bookworm_current_6.12.13_cinnamon-backported-mesa_desktop.img.xz edition. I think it might need a different nextcloud client for both editions. If one is using the authentication via browser and the other needs Gnome online accounts. Regards Norbert

Hi every time I start firefox an error message appears stating "Could not read configuration file - contact your system administrator" 🙃, i. e. me. Does anyone know how to fix it ? It is simply an annoyance - firefox works as expected so far. Kind regards Norbert

Hi I can access my nextcloud in the firefox browser, but the client always states "signed out". From time to time there is a request in the browser to confirm access of the client to the nextcloud server. Howeveer, this doesn't seem to work. I guess, I should add an online account (in Preferences). But there is no button to "Add account" shown. Do you have a hint to a missing package ? I am out of ideas how to solve it. Kind regards Norbert

Hi Yesterday I spend the whole day to install Armbian Desktop (XFCE) on my Pinebook Pro. Why Armbian ? The PBP was delivered with Manjaro Arm on it. Everything worked fine until Manjaro stopped support for the Arm platform. For about one year there is no update on stable and the unstable branch couldn't establish a connection to Wifi. I used Manjaro Arm to install tow-boot to the SPI following this website: https://forum.pine64.org/showthread.php?tid=17529 I downloaded the current Bookworm XFCE edition and wrote that to an SD card. Booting from the SD with tow-boot went fine. I installed armbian on the SD card and used armbian-config to install it on the internal eMMC. That didn't work. fsarchiver to the rescue ! I created a GPT partition table on the internal disk, created two partitions with the correct flags and restored both partitions from the SD saved with fsarchiver to the internal disk. Booting went fine from the internal disk after that. Now I am fighting with firefox ("Can't read configuration file - contact your systemadministrator") and the nextcloud client. I can't add a online account anywhere. The application starts up but there is no button execpt (Information about ...) which shows the supported clients a.o. Owncloud (which will work with nextcloud) but there is no way to add an account. I'll open other posts to track that.

My lsusb just shows the "ids" of the controller of connected drives but not the drives themselves. Neither the external disks nor the Ethernet HW were detected. I checked the directories/files in /etc/modules/6.1.x-meson64. The directory structures of kernel 6.1.11, 6.1.30 nd 6.1.42 are the same. However, kernel 6.1.11 seems to expect that the modules are compressed, it loads the modules and everything is fine for me. The filenames all end with .ko.xz while the modules from kernel 6.1.30 (Armbian bookworm version in the official download images) and the modules for kernel 6.1.42 are not compressed. Those filenames all end with .ko. I didn't check whether compressing the required modules (in kernel/drivers/firmware) can be loaded by the kernels 6.1.30 or 6.1.42 if they are compressed. So, if the first error message you see during reboot shows an error regarding "Failed: ...loading kernel modules" then try to compress the modules in /lib/modules/6.1.30-meson64/kernel/drivers/firmware and reboot. Hope this helps.