Support intro
Sorry to hear you’re facing problems. 
The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
I have a fresh install of nextcloud-aio as docker container.
The Basics
- Nextcloud Server version (e.g., 29.x.x):
not sure, I freshly pulled the image today, the description contains“Created”: “2025-10-24T08:02:33.407281516Z”
- Operating system and version (e.g., Ubuntu 24.04):
Ubuntu 24.04
- Web server and version (e.g, Apache 2.4.25):
replace me
- Reverse proxy and version _(e.g. nginx 1.27.2)
traefik 3.6.2
- PHP version (e.g, 8.3):
none
- Is this the first time you’ve seen this error? (Yes / No):
I'm noob trying to install nextcloud-aio via docker for the first time solvig one failure after the other ;)
- When did this problem seem to first start?
see above
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
Docker
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
no
Summary of the issue you are facing:
I first brought up a docker setup with traefik and a whoami app to make sure the basics are working. I can only reach my server via ipv6 (i don’t have a unique ipv4 adress from my provider). I can access the whoami app via my domain from the internet and get valid certificates via letsencrypt, so AAA records, etc. are correctly setup and the network is configured for ipv6.
I start the nextcloud-aio-mastercontainer in the docker-compose file and can access the first screen, opening https://[my_ipv6]:8080.
Clicking on “Open nextcloud AIO” yields in the message “Nextcloud AIO v11.11.0 Domaincheck container is not running”.
I already changed the APACHE_PORT to 11005, but this did not solve the issue.
When i check “docker container ls -a” I can see the nextcloud-aio-domaincheck container ist created but does not get started.
I find the error message “failed to set up container networking: driver failed programming external connectivity on endpoint nextcloud-aio-domaincheck (3f0d6f3848d6d0067d50e441ceadcbc576e7c5d5e09ef75ef7c7598df2425426): failed to bind host port [fd00:3::10]:11005/tcp: cannot assign requested address”} in the logs of the mastercontainer.
Nevertheless, when I manually start the domaincheck with “sudo docker container start nextcloud-aio-domaincheck” it is coming up and I can proceed in the browser with “Open nextcloud AIO”. => I suspect something is wrong in the way I set up the docker networking with assigning fixed ip addresses?
That’s where I fail the second time. I enter my domain to create a “New AIO instance”, click “Submit domain” and end up with “Domain does not point to this server or the reverse proxy is not configured correctly. See the mastercontainer logs for more details. (‘sudo docker logs -f nextcloud-aio-mastercontainer’)”
The error message is:
NOTICE: PHP message: The response of the connection attempt to "https://nc.seeniel.de:443" was: 404 page not found
NOTICE: PHP message: Expected was: ed088c8a0a1eeedb2325413794c0a8d45f9fbb8b1a8b8733
NOTICE: PHP message: The error message was:
NOTICE: PHP message: Please follow https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#how-to-debug in order to debug things!
I followed the how-to-debug as good as possible as my setup differs from the assumed. But APACHE_PORT and APACHE_IP_BINDING is assigned accordingy.
Please check if the server-url in the config/nextcloud-aio.yml below is pointint to the right port. I assigned it to 6080, which is pointing into the container to port 80. Should I have set it to 11005?
Nevertheless, if I use curl to try to connect to either port of the nextcloud-aio-mastercontainer I’m not able to.
Maybe you can point me to the right direction..
Steps to replicate it (hint: details matter!)
I guess it’s best to poste my docker-compose.yml and the configuration files here. I changed content which might identify me, if needed I can provide it.
docker-compose.yaml
services:
traefik:
image: traefik:latest
container_name: traefik
restart: unless-stopped
security_opt:
- no-new-privileges:true
environment:
- TZ=Europe/Amsterdam
networks:
# Connect to the 'traefik_proxy' overlay network for inter-container communication across nodes
proxy:
ipv6_address: fd00:2::10
nextcloud-aio:
ports:
- "80:80"
- "443:443"
# - "8080:8080"
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
- ./traefik.yml:/traefik.yml:ro # Traefik config file
- ./certs:/certs
- ./config:/config:ro
- ./logs:/logs
# Whoami application
whoami:
image: traefik/whoami
container_name: whoami
restart: unless-stopped
networks:
proxy:
ipv6_address: fd00:2::11
# Nextcloud-AIO application
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 # This line is not allowed to be changed as otherwise the built-in backup solution will not work
- /var/run/docker.sock:/var/run/docker.sock:ro # May be changed on macOS, Windows or docker rootless. See the applicable documentation. If adjusting, don't forget to also set 'WATCHTOWER_DOCKER_SOCKET_PATH'!
ports:
- "6080:80"
- "8080:8080"
environment: # Is needed when using any of the options below
- APACHE_PORT=11005 # Is needed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See
- APACHE_IP_BINDING=fd00:3::10 # Should be set when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else) that is running on the same host. See
networks:
nextcloud-aio:
ipv6_address: fd00:3::10
networks:
proxy:
name: proxy
enable_ipv6: true
driver: bridge
ipam:
driver: default
config:
- subnet: 172.18.0.0/16
gateway: 172.18.0.1
- subnet: fd00:2::/64
gateway: fd00:2::1
nextcloud-aio:
name: nextcloud-aio # This line is not allowed to be changed as otherwise the created network will not be used by the other containers of AIO
driver: bridge
enable_ipv6: true
ipam:
driver: default
config:
- subnet: fd00:3::/64 # IPv6 subnet to use
volumes: # If you want to store the data on a different drive, see
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer # This line is not allowed to be changed as otherwise the built-in backup solution will not work
traefik.yml
log:
filePath: "/logs/traefik_log.txt"
format: common
level: debug
accessLog:
format: json
filePath: "logs/traefik_access.log"
api:
dashboard: true # Optional can be disabled
insecure: false # Optional can be disabled
# debug: true # Optional can be Enabled if needed for troubleshooting
entryPoints:
web:
address: ":80"
# Optional if you want to redirect all HTTP to HTTPS
http:
redirections:
entryPoint:
to: websecure
scheme: https
websecure:
address: ":443"
#serversTransport:
# insecureSkipVerify: true
providers:
docker:
endpoint: "unix:///var/run/docker.sock"
exposedByDefault: false
network: proxy # Optional; Only use the "proxy" Docker network, even if containers are on multiple networks.
file:
directory: "/config"
watch: true
certificatesResolvers:
letsencrypt:
acme:
email: myemail@writeme.com
storage: /certs/acme.json
caServer: https://acme-v02.api.letsencrypt.org/directory # prod (default)
# caServer: https://acme-staging-v02.api.letsencrypt.org/directory # staging
tlsChallenge: true
config/nextcloud_aio.yml
http:
routers:
nextcloud:
rule: "Host(`nc.mydomain.com`)"
entrypoints:
- websecure
service: nextcloud-aio
tls:
certresolver: letsencrypt
services:
nextcloud-aio:
loadBalancer:
servers:
- url: "http://[fd00:3::10]:6080" # Use the host's IP address if Traefik runs outside the host network