Hello, since one of the reasons I wanted to work with Nextcloud on a Nextbox was that of collaborative editing on data physically located at my home, I looked for a way to run Collabora.
Unfortunately the internal app for the CODE server had issues downloading, and even after
forcing the download and install of the CODE server
logged in with SSH through
sudo docker exec -it -u www-data nexbox-compose_app_l php -d memory_limit=512M /var/www/html/occ app=install richdocumentscode_arm64
which completed successfully,
the server showed up as installed in the Nextcloud app administration, but no configuration was possible, and the Collabora app was trying to autoconfigure the existing server installation but could not get through.
A web search suggested to install the CODE as a
separate docker image
docker pull collabora/code@sha256:<hash> docker run -t -d -p 127.0.0.1:9980:9980 -e 'domain=<doubly escaped domain name>' -e "extra_params=--o:ssl.enable=false --o:ssl.termination=true" --restart always collabora/code
apt install apache2
/etc/apache2/apache2.conf to include a
but after a reboot this made the nextcloud installation not accessible anymore.
Connecting to the
nextbox.local url now only showed me the Apache2 Debian Default Page, removing any access to the Nextcloud instance. I had lost SSH access as well, since I uncarefully deactivated it from the inside of the Nextbox app before the last reboot. The green LED was fast-blinking for hours without any progress.
After retrieving a suitable monitor, video cable and keyboard to access the system directly, I noticed that the docker images kept reloading every 15-20s or so. I tried to revert the changes by first
deactivating the CODE docker container
docker update --restart=no <CODE docker container name> docker kill <CODE docker container name>
and after a reboot, I saw that at least the 4 nextcloud-compose docker containers stayed loaded, and the green LED in continuous-on, but no access from the outside to the nextcloud instance yet (still apache default page).
removed the apache package
apt remove --autoremove apache2
as well and commented the modified line to
but could not further revert the situation.
Any tips or suggestions on what to look for or what to do in order to recover the starting state? I had no data saved nor personal services configured yet (except for some dummy data for tryouts), but I would prefer to avoid physically opening the Nextbox itself.