The Basics
- Nextcloud Server version:
- AIO Version 10.4.0
- Operating system and version:
- OpenMediaVault 7.5.2 (Debian 12)
- Web server and version:
- AIO Built-in
- Reverse proxy and version
- Nginx 1.22, hosted on raspberry pi 2 (different computer) in same network
- PHP version:
- AIO Built-in
- Is this the first time you’ve seen this error? (Yes / No):
- Yes
- When did this problem seem to first start?
- When I started the AIO container (for the first time)
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
- AIO Docker Compose
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
- No
Summary of the issue you are facing:
Domaincheck container won’t install and apache port 11000 seemingly inaccessible.
Steps to replicate it (hint: details matter!):
- Setup AIO using existing reverse proxy instructions
- Setup nginx to manage IP.of.nextcloud.server:11000. (pretty sure this doesn’t matter since this happens before domaincheck when I first boot the container)
Log entries
Mastercontainer logs:
{"level":"info","ts":1737931931.7922266,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1737931931.7945788,"msg":"adapted config to JSON","adapter":"caddyfile"}
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: read udp [::1]:57257->[::1]:53: read: connection refused
NOTICE: PHP message: Could not get digest of container nextcloud/aio-domaincheck:latest cURL error 6: Could not resolve host: auth.docker.io (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://auth.docker.io/token?service=registry.docker.io&scope=repository:nextcloud/aio-domaincheck:pull
I’ve tried a lot of things related to internet access and DNS. I know the container can resolve DNS addresses. Here’s some logs from nslookup run inside the container.
194247f17fb9:/# nslookup auth.docker.io
Server: 192.168.1.100
Address: 192.168.1.100:53
Non-authoritative answer:
Name: auth.docker.io
Address: 98.85.153.80
Name: auth.docker.io
Address: 3.94.224.37
Name: auth.docker.io
Address: 44.208.254.194
Non-authoritative answer:
Name: auth.docker.io
Address: 2600:1f18:2148:bc00:5cac:48a0:7f88:7266
Name: auth.docker.io
Address: 2600:1f18:2148:bc01:f43d:e203:cafd:8307
Name: auth.docker.io
Address: 2600:1f18:2148:bc02:22:27bd:19a8:870c
194247f17fb9:/# nslookup localhost
Server: 192.168.1.100
Address: 192.168.1.100:53
Name: localhost.lan
Address: 127.0.0.1
Name: localhost.lan
Address: ::1
Web server / Reverse Proxy
No relevant output for nginx, as everything thus far is happening through the AIO device IP. Running
nc -z 192.168.1.101 11000; echo $?
where “192.168.1.101” is the IP of the AIO device, gives “1”.
Configuration
Side note: I tried completely uninstalling the AIO container and reinstalling without a reverse proxy and with the default compose.yaml from the github page and it gave the exact same error, so it may be related to openmediavault or some other system configuration issue.
services:
nextcloud-aio-mastercontainer:
image: nextcloud/all-in-one:latest
init: true
restart: always
container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not work correctly
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config
- /var/run/docker.sock:/var/run/docker.sock:ro
network_mode: bridge
ports:
- 8080:8080
environment:
AIO_DISABLE_BACKUP_SECTION: true
AIO_COMMUNITY_CONTAINERS:
APACHE_PORT: 11000
APACHE_IP_BINDING: 192.168.1.101
NEXTCLOUD_DATADIR: /srv/mergerfs/data/nextcloud
NEXTCLOUD_MOUNT: /srv/mergerfs/data/media
NEXTCLOUD_ENABLE_DRI_DEVICE: true
# TALK_PORT: 3478
volumes:
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer
Nextcloud
When running: php occ config:list system
inside the container.
Could not open input file: occ