Hello,
I’m trying to install Nextcloud AIO by deploying a stack using Portainer in an Asustor NAS (AS6704T) which is running the latest version of ADM (Asustor’s OS). I can pass the login screen but in the next screen I get the following error:
Nextcloud AIO v7.6.2
Domaincheck container is not running
This is not expected. Most likely this happened because port 12345 is already in use on your server. You can check the mastercontainer logs and domaincheck container logs for further clues. You should be able to resolve this by adjusting the APACHE_PORT by following the reverse proxy documentation . Advice: have a detailed look at the changed docker run command for AIO.
Here is the entire log in mastercontainer:
Trying to fix docker.sock permissions internally...
Adding internal www-data to group root
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled
.+.+.....+.........+.......+...+.....+....+......+...........+...+.+.....+.+......+..+++++++++++++++++++++++++++++++++++++++++++++*.+...+............+++++++++++++++++++++++++++++++++++++++++++++*.+..+....+..........................+...+................+..+...+.+.....................+.....+.............+......+...+.....+.......+..............+..........+...............+.....+....+..+.+..+...+....+.........+...........+...+.+..+.........+.....................+............+.............+............+..+.+........+.+++++
.+...+......+.+......+...............+.....+...+++++++++++++++++++++++++++++++++++++++++++++*...........+...+++++++++++++++++++++++++++++++++++++++++++++*...............+........+......................+...+.........+...+.....+.......+......+..+....+........+.+..+.........+...+.......+.........+......+...............+.....+......+...+............+....+.....+.........+.+......+..+.............+..+.+.....+.........+.......+...+...+............+..+.........+....+...............+......+......+..................+..+..................+.+...........+......+++++
-----
Initial startup of Nextcloud All-in-One complete!
You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
E.g. https://internal.ip.of.this.server:8080
If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:
https://your-domain-that-points-to-this-server.tld:8443
INF ts=1700057702.6758084 msg=using provided configuration config_file=/Caddyfile config_adapter=
[Wed Nov 15 14:15:02.677054 2023] [mpm_event:notice] [pid 120:tid 140196131933000] AH00489: Apache/2.4.58 (Unix) OpenSSL/3.1.4 configured -- resuming normal operations
[Wed Nov 15 14:15:02.677104 2023] [core:notice] [pid 120:tid 140196131933000] AH00094: Command line: 'httpd -D FOREGROUND'
[15-Nov-2023 14:15:02] NOTICE: fpm is running, pid 126
[15-Nov-2023 14:15:02] NOTICE: ready to handle connections
NOTICE: PHP message: Could not start domaincheck container: Client error: `POST http://localhost/v1.41/containers/nextcloud-aio-domaincheck/start` resulted in a `400 Bad Request` response:
{"message":"failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process (truncated...)
The “nextcloud-aio-domaincheck” container is in “created” status but it’s log is empty.
If I try to start it manually I get a 400 error.
Here is my docker compose:
services:
nextcloud-aio-mastercontainer:
image: nextcloud/all-in-one:latest
init: true
restart: always
container_name: nextcloud-aio-mastercontainer
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config
- /var/run/docker.sock:/var/run/docker.sock:ro
ports:
- 49080:8080
environment:
- APACHE_PORT=12345
- APACHE_IP_BINDING=0.0.0.0
- NEXTCLOUD_DATADIR=/share/nextcloud-data
- NEXTCLOUD_MOUNT=/share/Datos/
- SKIP_DOMAIN_VALIDATION=true
volumes:
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer
I have checked that “docker.sock” is located in “/var/run” in the host:
My intention is to run Nextcloud AIO behind a reverse proxy in Nginx Proxy Manager running in a separate container in the same NAS, but I have tested other methods without reverse proxy and I’m always stuck in the same error.
In the /etc/host file inside the NPM container, the host.docker.internal is pointing to 172.17.0.1.
Here is my NPM configuration:
I don’t think it’s something related to the reverse proxy because in some videos or other threads I have seen searching in Internet, those issues showed a more specific message in log and happened in a further step after the Domain checker runs in the AIO interface.
I have tried almost everything:
- Using the default configuration without a reverse proxy.
- Using the default ports.
- Using different ports in APACHE_PORT env variable.
- Using the default docker compose in order to check if I can get pass this error without a reverse proxy.
- Using docker commands in terminal instead of docker compose nor Portainer.
- Change the IP of the NPM entry by to the host IP instead of the IP provided by “host.docker.internal”.
- Change network mode from NPM container to “host” as suggested in https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#adaptation-of-the-respective-sample-configuration
I have figured out that is something related with the network, because every time I try to run a fresh install using different ports (no matter if I map APACHE_PORT or not) the problem remains is the same.
I have made a fresh install of the stack every time I tried something different without succeed.
I hope someone can help me.
Thanks in advance.
Best regards.
