I think after the last update of the master container, all the other containers are working fine and I can use nextcloud. Took me sometime to realize 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 https://dockerlabs.collabnix.com/intermediate/networking/Configuring_DNS.html

Another solution is using https://github.com/nextcloud/all-in-one/tree/main/manual-install

I found somewhere online that the DNS could be the issue, no other containers have issues and I can update them. I setup the DNS in unraid to 1.1.1.1 to make sure that the DNS is working.

Does anyone knows what I could do to solve this?

Should I just delete the master container and reinstall? Or delete all the containers are recover from the backup? I would like to avoid the backup option if possible because it is always a little scary.

Thanks, hopefully here is the correct place to ask this.

I don't know if you still needs help but I just ran into the same issue, the reason why this happened to me is when rebooting the server the Nextcloud AIO somehow used the default port 8080 instead of what I set the port as in the setting. I had to go into setting, type in the port again, and click apply to restart the container to fix this. It's been running normally since.

I ended up reinstalling the container with the previous settings and now the container starts but I cannot access the webUI. I'm using port 7282 as webui like default but that does not work. Even if I try to open the AIO from nextcloud it does not connect. Nextcloud has been working fine all this time.

The log for the master container is like this now:

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 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
{"level":"info","ts":1755281567.649624,"msg":"maxprocs: Leaving GOMAXPROCS=6: CPU quota undefined"}
{"level":"info","ts":1755281567.6498203,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":30181456281,"previous":9223372036854775807}
{"level":"info","ts":1755281567.6498535,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1755281567.6509106,"msg":"adapted config to JSON","adapter":"caddyfile"}
{"level":"info","ts":1755281567.6616337,"msg":"serving initial configuration"}
[Fri Aug 15 18:12:47.712314 2025] [mpm_event:notice] [pid 150:tid 150] AH00489: Apache/2.4.65 (Unix) OpenSSL/3.5.1 configured -- resuming normal operations
[Fri Aug 15 18:12:47.712365 2025] [core:notice] [pid 150:tid 150] AH00094: Command line: 'httpd -D FOREGROUND'
[15-Aug-2025 18:12:47] NOTICE: fpm is running, pid 156
[15-Aug-2025 18:12:47] 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

It says that I should use port 8080 but, even using that port does not connect to the master container.

I'm kind of not sure now what could I do more. If I unistall all the containers and try to install the master container again I have no idea if it would actually work. At least for now nextcloud still works.

On 8/13/2025 at 12:59 PM, xykstchh said:

I don't know if you still needs help but I just ran into the same issue, the reason why this happened to me is when rebooting the server the Nextcloud AIO somehow used the default port 8080 instead of what I set the port as in the setting. I had to go into setting, type in the port again, and click apply to restart the container to fix this. It's been running normally since.

I'll be... that fixed it! Not sure I'd have ever solved it otherwise, thank you!

On 8/13/2025 at 6:59 PM, xykstchh said:

I don't know if you still needs help but I just ran into the same issue, the reason why this happened to me is when rebooting the server the Nextcloud AIO somehow used the default port 8080 instead of what I set the port as in the setting. I had to go into setting, type in the port again, and click apply to restart the container to fix this. It's been running normally since.

Thank you so much. This simple answer saved my evening.