getting error Domaincheck container is not running - Even if --env SKIP_DOMAIN_VALIDATION=true set #5904
-
Steps to reproduceJust follow this doc https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
sudo docker run \
--init \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 8080:8080 \
--env APACHE_PORT=11000 \
--env APACHE_IP_BINDING=0.0.0.0 \
--env APACHE_ADDITIONAL_NETWORK="" \
--env SKIP_DOMAIN_VALIDATION=false \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
nextcloud/all-in-one:latest
Expected behaviorI should be able to setup / access next cloud Actual behaviorLogs: 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: Other informationHost OSubuntu 24 Output of
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
After debugging - it looks like AIO master is not pulling / building images. as mine is a fresh install, I don't / won't be having any nextcloud container |
Beta Was this translation helpful? Give feedback.
-
@szaimen |
Beta Was this translation helpful? Give feedback.
-
Hi, can you follow https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#6-how-to-debug-things? |
Beta Was this translation helpful? Give feedback.
Hi, can you follow https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#6-how-to-debug-things?