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).
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. 
The Basics
- Nextcloud Server version (e.g., 29.x.x):
- Nextcloud AIO v11.7.0
- Operating system and version (e.g., Ubuntu 24.04):
Debian 12
- Web server and version (e.g, Apache 2.4.25):
replace me
- Reverse proxy and version _(e.g. nginx 1.27.2)
nginxv2.12.6
- PHP version (e.g, 8.3):
replace me
- Is this the first time you’ve seen this error? (Yes / No):
yes
- When did this problem seem to first start?
From first installation
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
AIOdocker on OpenMediaVault
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
no
Summary of the issue you are facing:
After login with passphrase i get this:
Nextcloud AIO v11.7.0
Domaincheck container is not running
This is not expected. Most likely this happened because port 11000 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.
This is yml for container:
services:
nextcloud-aio-mastercontainer:
image: ghcr.io/nextcloud-releases/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: - 8080:8080
environment: - APACHE_PORT=11000
- APACHE_IP_BINDING=127.0.0.1
- NEXTCLOUD_DATADIR=/srv/dev-disk-by-uxxxx-0b673f98fdd4/data/nextcloud
- NEXTCLOUD_MOUNT=/srv/dev-disk-by-xxxx-0b673f98fdd4/data/media/
#- TALK_PORT=3679
volumes:
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer
Tried with adding dns:
cat /etc/docker/daemon.json
{
“data-root”: “/srv/dev-disk-by-xxx/docker”
“dns”: [“8.8.8.8”, “1.1.1.1”]
}
TEsting:
nano /etc/docker/daemon.json
root@xxx:~# systemctl restart docker
root@xxx:~# docker info | grep DNS
root@xxx:~# docker run --rm busybox nslookup ghcr.io
Unable to find image ‘busybox:latest’ locally
latest: Pulling from library/busybox
80bfbb8a41a2: Pull complete
Digest: sha2xxxxx
Status: Downloaded newer image for busybox:latest
Server: 8.8.8.8
Address: 8.8.8.8:53
Non-authoritative answer:
Non-authoritative answer:
Name: ghcr.io
Address: 140.82.121.33
Its my first time to deal with NextCloud
As I understand, for nextcloud-aio-mastercontainer with reverse proxy i do not need this “nextcloud-aio-domaincheck“, and i dont have it as image in yml, but it keeps trying to create:
dont know why im getting error “URL error 6: Could not resolve host: ghcr.io“ if I can ping it:
root@xxx:~# docker exec -it nextcloud-aio-mastercontainer /bin/bash
fd031dssad6xxb8:/var/www/docker-aio# ping ghcr.io
PING ghcr.io (140.82.121.34): 56 data bytes
64 bytes from 140.82.121.34: seq=0 ttl=51 time=45.202 ms
64 bytes from 140.82.121.34: seq=1 ttl=51 time=47.031 ms
64 bytes from 140.82.121.34: seq=2 ttl=51 time=47.043 ms
Steps to replicate it (hint: details matter!):
-
Installed ngingx and configured like in
all-in-one/reverse-proxy.md at main · nextcloud/all-in-one -
Installing container nextcloud-aio-mastercontainer
-
after login with passphrase i get that Domaincheck container is not running
Log entries
Nextcloud
Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.
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
⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!
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
/usr/lib/python3.12/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
import pkg_resources
[Sat Sep 13 21:48:43.631198 2025] [mpm_event:notice] [pid 173:tid 173] AH00489: Apache/2.4.65 (Unix) OpenSSL/3.5.2 configured -- resuming normal operations
[Sat Sep 13 21:48:43.631238 2025] [core:notice] [pid 173:tid 173] AH00094: Command line: 'httpd -D FOREGROUND'
{"level":"info","ts":1757800123.6388743,"msg":"maxprocs: Leaving GOMAXPROCS=8: CPU quota undefined"}
{"level":"info","ts":1757800123.639134,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":29622734438,"previous":9223372036854775807}
{"level":"info","ts":1757800123.63919,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1757800123.640178,"msg":"adapted config to JSON","adapter":"caddyfile"}
[13-Sep-2025 21:48:43] NOTICE: fpm is running, pid 179
[13-Sep-2025 21:48:43] NOTICE: ready to handle connections
{"level":"info","ts":1757800123.6409214,"msg":"maxprocs: No GOMAXPROCS change to reset"}
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: read udp [::1]:44425->[::1]:53: read: connection refused
{"level":"info","ts":1757800124.6815026,"msg":"maxprocs: Leaving GOMAXPROCS=8: CPU quota undefined"}
{"level":"info","ts":1757800124.6816704,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":29622734438,"previous":9223372036854775807}
{"level":"info","ts":1757800124.681696,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1757800124.6825526,"msg":"adapted config to JSON","adapter":"caddyfile"}
{"level":"info","ts":1757800124.6834552,"msg":"maxprocs: No GOMAXPROCS change to reset"}
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: read udp [::1]:33531->[::1]:53: read: connection refused
{"level":"info","ts":1757800126.7247262,"msg":"maxprocs: Leaving GOMAXPROCS=8: CPU quota undefined"}
{"level":"info","ts":1757800126.7249002,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":29622734438,"previous":9223372036854775807}
{"level":"info","ts":1757800126.7249296,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1757800126.7257826,"msg":"adapted config to JSON","adapter":"caddyfile"}
{"level":"info","ts":1757800126.7265444,"msg":"maxprocs: No GOMAXPROCS change to reset"}
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: read udp [::1]:36130->[::1]:53: read: connection refused
{"level":"info","ts":1757800129.7696204,"msg":"maxprocs: Leaving GOMAXPROCS=8: CPU quota undefined"}
{"level":"info","ts":1757800129.769811,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":29622734438,"previous":9223372036854775807}
{"level":"info","ts":1757800129.7698388,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1757800129.7707255,"msg":"adapted config to JSON","adapter":"caddyfile"}
{"level":"info","ts":1757800129.7715194,"msg":"maxprocs: No GOMAXPROCS change to reset"}
Error: loading initial config: loading new config: starting caddy administration endpoint: listen tcp: lookup localhost on [::1]:53: read udp [::1]:33914->[::1]:53: read: connection refused
NOTICE: PHP message: Could not get digest of container nextcloud-releases/aio-domaincheck:latest cURL error 6: Could not resolve host: ghcr.io (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://ghcr.io/token?scope=repository:nextcloud-releases/aio-domaincheck:pull
NOTICE: PHP message: Not pulling the ghcr.io/nextcloud-releases/aio-domaincheck image for the nextcloud-aio-domaincheck container because the registry does not seem to be reachable.
NOTICE: PHP message: Could not start domaincheck container: Could not create container nextcloud-aio-domaincheck: {"message":"No such image: ghcr.io/nextcloud-releases/aio-domaincheck:latest"}
NOTICE: PHP message: Could not get digest of container nextcloud-releases/all-in-one:latest cURL error 6: Could not resolve host: ghcr.io (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://ghcr.io/token?scope=repository:nextcloud-releases/all-in-one:pull
Web Browser
If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.
PASTE
Web server / Reverse Proxy
The output of your Apache/nginx/system log in /var/log/____:
PASTE HEREapp-1 | [9/13/2025] [9:03:53 PM] [SSL ] › ℹ info Renewing SSL certs expiring within 30 days ...
app-1 | [9/13/2025] [9:03:53 PM] [SSL ] › ℹ info Completed SSL cert renew process
app-1 | [9/13/2025] [9:11:40 PM] [Global ] › ℹ info PID 183 received SIGTERM
app-1 | [9/13/2025] [9:11:40 PM] [Global ] › ℹ info Stopping.
app-1 | e[1;34m❯ e[1;36mConfiguring npm user ...e[0m
app-1 | 0
app-1 | usermod: no changes
app-1 | e[1;34m❯ e[1;36mConfiguring npm group ...e[0m
app-1 | e[1;34m❯ e[1;36mChecking paths ...e[0m
app-1 | e[1;34m❯ e[1;36mSetting ownership ...e[0m
app-1 | - /data ...
app-1 | SKIPPED
app-1 | - /etc/letsencrypt ...
app-1 | SKIPPED
app-1 | - /run/nginx ...
app-1 | SKIPPED
app-1 | - /tmp/nginx ...
app-1 | SKIPPED
app-1 | - /var/cache/nginx ...
app-1 | SKIPPED
app-1 | - /var/lib/logrotate ...
app-1 | SKIPPED
app-1 | - /var/lib/nginx ...
app-1 | SKIPPED
app-1 | - /var/log/nginx ...
app-1 | SKIPPED
app-1 | - /etc/nginx/nginx ...
app-1 | SKIPPED
app-1 | - /etc/nginx/nginx.conf ...
app-1 | SKIPPED
app-1 | - /etc/nginx/conf.d ...
app-1 | SKIPPED
app-1 | e[1;34m❯ e[1;36mChanging ownership of certbot directories, this may take some time ...e[0m
app-1 | - /opt/certbot ...
app-1 | SKIPPED
app-1 | - /opt/certbot/bin ...
app-1 | SKIPPED
app-1 | - /opt/certbot/lib/python3.11/site-packages ...
app-1 | SKIPPED
app-1 | e[1;34m❯ e[1;36mDynamic resolvers ...e[0m
app-1 | e[1;34m❯ e[1;36mIPv6 ...e[0m
app-1 | Enabling IPV6 in hosts in: /etc/nginx/conf.d
app-1 | - /etc/nginx/conf.d/default.conf
app-1 | - /etc/nginx/conf.d/include/block-exploits.conf
app-1 | - /etc/nginx/conf.d/include/assets.conf
app-1 | - /etc/nginx/conf.d/include/proxy.conf
app-1 | - /etc/nginx/conf.d/include/force-ssl.conf
app-1 | - /etc/nginx/conf.d/include/ssl-ciphers.conf
app-1 | - /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
app-1 | - /etc/nginx/conf.d/include/log.conf
app-1 | - /etc/nginx/conf.d/include/ssl-cache.conf
app-1 | - /etc/nginx/conf.d/include/ssl-cache-stream.conf
app-1 | - /etc/nginx/conf.d/include/ip_ranges.conf
app-1 | - /etc/nginx/conf.d/include/resolvers.conf
app-1 | - /etc/nginx/conf.d/production.conf
app-1 | Enabling IPV6 in hosts in: /data/nginx
app-1 | - /data/nginx/proxy_host/2.conf
app-1 | e[1;34m❯ e[1;36mDocker secrets ...e[0m
app-1 |
app-1 | -------------------------------------
app-1 | _ _ ____ __ __
app-1 | | \ | | _ \| \/ |
app-1 | | \| | |_) | |\/| |
app-1 | | |\ | __/| | | |
app-1 | |_| \_|_| |_| |_|
app-1 | -------------------------------------
app-1 | User: npm PUID:0 ID:0 GROUP:0
app-1 | Group: npm PGID:0 ID:0
app-1 | -------------------------------------
app-1 |
app-1 | e[1;34m❯ e[1;36mStarting nginx ...e[0m
app-1 | e[1;34m❯ e[1;36mStarting backend ...e[0m
app-1 | [9/13/2025] [9:11:47 PM] [Global ] › ℹ info Using MySQL configuration
app-1 | [9/13/2025] [9:11:48 PM] [Migrate ] › ℹ info Current database version: 20240427161436
app-1 | [9/13/2025] [9:11:48 PM] [Setup ] › ℹ info Logrotate Timer initialized
app-1 | [9/13/2025] [9:11:48 PM] [Global ] › ⬤ debug CMD: logrotate /etc/logrotate.d/nginx-proxy-manager
app-1 | [9/13/2025] [9:11:48 PM] [Setup ] › ℹ info Logrotate completed.
app-1 | [9/13/2025] [9:11:48 PM] [Global ] › ℹ info IP Ranges fetch is enabled
app-1 | [9/13/2025] [9:11:48 PM] [IP Ranges] › ℹ info Fetching IP Ranges from online services...
app-1 | [9/13/2025] [9:11:48 PM] [IP Ranges] › ℹ info Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
app-1 | [9/13/2025] [9:11:48 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v4
app-1 | [9/13/2025] [9:11:48 PM] [IP Ranges] › ℹ info Fetching https://www.cloudflare.com/ips-v6
app-1 | [9/13/2025] [9:11:48 PM] [SSL ] › ℹ info Let's Encrypt Renewal Timer initialized
app-1 | [9/13/2025] [9:11:48 PM] [SSL ] › ℹ info Renewing SSL certs expiring within 30 days ...
app-1 | [9/13/2025] [9:11:48 PM] [IP Ranges] › ℹ info IP Ranges Renewal Timer initialized
app-1 | [9/13/2025] [9:11:48 PM] [Global ] › ℹ info Backend PID 175 listening on port 3000 ...
app-1 | [9/13/2025] [9:11:48 PM] [SSL ] › ℹ info Completed SSL cert renew process
app-1 | [9/13/2025] [9:47:56 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;"
app-1 | [9/13/2025] [9:47:56 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/2.conf
app-1 | [9/13/2025] [9:47:56 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;"
app-1 | [9/13/2025] [9:47:56 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;"
app-1 | [9/13/2025] [9:47:56 PM] [Nginx ] › ℹ info Reloading Nginx
app-1 | [9/13/2025] [9:47:56 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload
Configuration
Nextcloud
The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):
PASTE HERE
Apps
The output of occ app:list (if possible).
Tips for increasing the likelihood of a response
- Use the
preformatted textformatting option in the editor for all log entries and configuration output. - If screenshots are useful, feel free to include them.
- If possible, also include key error output in text form so it can be searched for.
- Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.