At last, got all running. And in hindsight, what took me so long? Well to mention a few:
Host opensuse did do some odd things after enabled modules in Apache, the loaded modules were put in another file which did not get loaded. After that was fixed, all kind of directives at last started to work. Then I had to switch the way Docker ran the containers (for I used the script ânot behind reverse proxyâ ⌠And of course I made some typoâs in the ports used and IP addresses⌠And I was not (yet) able to run the DNS-PERSIST-01 challenge with the now current certbot binary on my host. So after some three months I still have to renew my DNS-01 certificates manually. And yes, it took some time to discover that I did forget to open the appropriate ports (tcp and udp) in my firewall, all after I figured out in what zone my server would live and which command to use to manipulate the settings.
To kill all (running) docker containers and be able to restart all I did create a stopkill.sh file:
#!/bin/bash
cNCc="$( sudo docker ps -a | grep aio-mastercontainer | cut -f 1 -d ' ' )"
sudo docker stop ${cNCc}
sudo docker stop $(docker ps -a -q)
sudo docker rm $(docker ps -a -q)
And to (re)start the instance (with a refresh of the master container) I now use start_nc.sh
#!/bin/bash
# For Linux and with a web server or reverse proxy already in place:
cNCc="$( sudo docker ps -a | grep aio-mastercontainer | cut -f 1 -d ' ' )"
sudo docker stop ${cNCc}
sudo docker rm ${cNCc}
sudo docker pull ghcr.io/nextcloud-releases/all-in-one:latest
sudo docker run \
--env NEXTCLOUD_MOUNT="/cloudlocation/" \
--env NEXTCLOUD_DATADIR="/cloudlocation" \
--env APACHE_PORT=8182 \
--env APACHE_IP_BINDING=<internalIP> \
--env APACHE_ADDITIONAL_NETWORK="" \
--env SKIP_DOMAIN_VALIDATION=false \
--init \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 8181:8080 \
--security-opt label:disable \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
-d ghcr.io/nextcloud-releases/all-in-one:latest
After running this script I can go to http://{internalIP}:8181 (and allow self-signed AIO management page to load) and start (and refresh) all containers.
Note: I picked up the -d flag to detach the docker container to run in the background. It is not in the provided run script (I have no idea yet how to use compose.yaml). I also created an executable âdoccâ command in my ~/bin/ dir with this content:
sudo docker exec --user www-data -it nextcloud-aio-nextcloud php /var/www/html/occ ${1} ${2} ${3} ${4} ${5} ${6} ${7} ${8} ${9} ${10} ${11} ${12}
which serves as a commandline occ replacement but then from outside the container (usable in a ssh shell / cli of the headless cloudserver)
Had to fix /etc/apache2/httpd.conf to load the a2enmod modules (from /etc/apache2/sysconfig.d/loadmodule.conf instead of /etc/apache2/loadmodule.conf) The default vhost.conf example for Apache did the job quite well, other directives to allow real IP addresses in logs etc, still have to be done (because mod_rewrite was not loaded, see loadmodule issue above, these settings kept throwing me errors. Should be good to redo that part now. And oh, mod_security2, I have to look into that one too yet. And then I did setup my primary fallback vhost and my cloudserver as wel as all other vhosts in the /etc/apache2/vhost.d/allhosts.conf file with plenty of settings to finetune still.
Then at last had to set the proper way of parameters in /var/lib/docker/volumes/nextcloud_aio_nextcloud/_data/config/config.phpespecially for the 'trusted_proxies' => array where âlocalhostâ was not appreciated⌠And I found out that setting entries in the config.php using docc was, well, not always correctâŚ
In the end, I think it is working again. Now as one of several hosted sites on the 2nd-live old work computer. All in all, yes, it was all documented (and well documented) but all those words were playing hard-to-grasp in my mind. Hence a brief description of a lot of hours searching and trying. Sorry for the WallOfText.
And one more issue: Running Nextcloud 33.0.3.2 NOT on latest patch level
Major version still supported Scanned at 2026-06-04 22:44:47