The Basics
- Nextcloud Server version (e.g., 29.x.x):
- 31.0.7
- Operating system and version (e.g., Ubuntu 24.04):
- unraid
- Web server and version (e.g, Apache 2.4.25):
replace me
- Reverse proxy and version _(e.g. nginx 1.27.2)
- nginx proxy manager
- PHP version (e.g, 8.3):
- 8.3.23
- Is this the first time you’ve seen this error? (Yes / No):
- yes
- When did this problem seem to first start?
- some weeks ago after an update of the AIO
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
- AIO
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
- cloudflare
Summary of the issue you are facing:
I’m using the unriad community app AIO master container.
I think after the last update of the master container this started happening and the container is not starting, all the other containers are working fine and I can use nextcloud. Took me sometime to realise that the master container was not started because everything looked fine.
When I check the logs I get this message:
Could not reach https://ghcr.io.
Most likely is something blocking access to it.
You should be able to fix this by following Configuring DNS | dockerlabs
Another solution is using all-in-one/manual-install at main · nextcloud/all-in-one · GitHub
I could not find a solution to this issue and I reinstalled the AIO master container. All the containers created by it are working still. After the reinstall, the master container starts but I cannot connect to its web UI.
The port I set up is 7282 but the log of the container says to access it from port 8080. Neither work. Even the link from the nextcloud to open the AIO does not work.
I’m using nginx proxy manager to point a nextcloud.domain.com to the port 11000 (apache port).
Now when I check the logs of the AIO container I get:
WARNING: No swap limit support
WARNING: No swap limit support
/usr/lib/python3.12/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See Package Discovery and Resource Access using pkg_resources - setuptools 80.10.2 documentation. 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
{“level”:“info”,“ts”:1755108205.7699456,“msg”:“maxprocs: Leaving GOMAXPROCS=6: CPU quota undefined”}
{“level”:“info”,“ts”:1755108205.7701674,“msg”:“GOMEMLIMIT is updated”,“package”:“github.com/KimMachineGun/automemlimit/memlimit",“GOMEMLIMIT”:30181456281,"previous”:9223372036854775807}
{“level”:“info”,“ts”:1755108205.770197,“msg”:“using config from file”,“file”:“/Caddyfile”}
{“level”:“info”,“ts”:1755108205.771037,“msg”:“adapted config to JSON”,“adapter”:“caddyfile”}
[Wed Aug 13 18:03:25.774859 2025] [mpm_event:notice] [pid 153:tid 153] AH00489: Apache/2.4.65 (Unix) OpenSSL/3.5.1 configured – resuming normal operations
[Wed Aug 13 18:03:25.774889 2025] [core:notice] [pid 153:tid 153] AH00094: Command line: ‘httpd -D FOREGROUND’
{“level”:“info”,“ts”:1755108205.7806306,“msg”:“serving initial configuration”}
[13-Aug-2025 18:03:25] NOTICE: fpm is running, pid 158
[13-Aug-2025 18:03:25] NOTICE: ready to handle connections
Trying to fix docker.sock permissions internally…
Creating docker group internally with id 281
The environmental variable TZ has been set which is not supported by AIO since it only supports running in the default Etc/UTC timezone!
The correct timezone can be set in the AIO interface later on!
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
How can I connect to the AIO master container? It has been working fine for months before this and I did not change anything else but update the AIO master container.
Steps to replicate it (hint: details matter!):
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.
PASTE HERE
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 HERE
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.