Mastercontainer update not working

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

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:

(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. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 31.0.10.2 (from AIO v.12.7)
  • Operating system and version (e.g., Ubuntu 24.04):
    • Debian 12.10
  • Web server and version (e.g, Apache 2.4.25):
    • Docker AIO
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • nginx 1.14.2
  • PHP version (e.g, 8.3):
    • Docker AIO
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • Today
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • AIO
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

I got a notification about a master container update. However, after that the host that serves Nextcloud and other stuff stopped working (a different service had saturated disk space). I fixed the issue (identified the offending service, stopped it, freed space) and restarted Docker containers, which started ok, including Nextcloud ones.

However, Nextcloud now returns Bad Gateway, and if I go to https://<host_ip>:8080/containers I get the “Update mastercontainer” button. This is not new to me, so I just click on it, but after a short while that same screen comes back (this is new). I’m stuck in an “update mastercontainer” loop and I can’t get out of it.

I’ve already tried stopping all the containers, deleting stopped containers, rebooting the machine and so on. Initially, the logs talked about a certificate issue: I had installed a custom self-signed CA and I had run update-ca-certificates, after which I had to re-add as trusted CAs some domains like gchr.io and github.com. After re-adding them, the logs didn’t show the error any more, but the loop was still there.

I’ve tried to manually run docker pull ``gchr.io/nextcloud-releases/all-in-one, and I got once again error pulling image configuration: download failed after attempts=6: tls: failed to verify certificate: x509: certificate signed by unknown authority. This seems weird, as I had added the CA certificate for gchr.io, but it’s possible that I missed something; however, I don’t have any confirmation of the domain whose SSL connection fails, so I don’t know what to do.

Steps to replicate it (hint: details matter!):

Erm… have docker fail while a mastercontainer update is pending? Sorry, but I can’t say what caused the error.

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.

Note: nextcloud.log contains 583 lines. After scanning it, I’m posting those that I think are more relevant. Let me know if I need to post something else.

{"reqId":"fdq97DOQSkL4rmGMvdQ0","level":0,"time":"2025-11-19T17:21:26+00:00","remoteAddr":"","user":"--","app":"core","method":"","url":"--","message":"starting upgrade from 31.0.10.2 to 32.0.1.2","userAgent":"--","version":"31.0.10.2","data":{"app":"core"}}
{"reqId":"fdq97DOQSkL4rmGMvdQ0","level":1,"time":"2025-11-19T17:21:26+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"OC\\Repair\\Events\\RepairStepEvent: Repair step: Repair MySQL collation","userAgent":"--","version":"31.0.10.2","data":{"app":"updater"}}
{"reqId":"fdq97DOQSkL4rmGMvdQ0","level":1,"time":"2025-11-19T17:21:26+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"OC\\Repair\\Events\\RepairInfoEvent: Repair info: Not a mysql database -> nothing to do","userAgent":"--","version":"31.0.10.2","data":{"app":"updater"}}
{"reqId":"fdq97DOQSkL4rmGMvdQ0","level":1,"time":"2025-11-19T17:21:26+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"OC\\Repair\\Events\\RepairStepEvent: Repair step: Copy data from accounts table when migrating from ownCloud","userAgent":"--","version":"31.0.10.2","data":{"app":"updater"}}
{"reqId":"fdq97DOQSkL4rmGMvdQ0","level":1,"time":"2025-11-19T17:21:27+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"OC\\Repair\\Events\\RepairStepEvent: Repair step: Drop account terms table when migrating from ownCloud","userAgent":"--","version":"31.0.10.2","data":{"app":"updater"}}
{"reqId":"fdq97DOQSkL4rmGMvdQ0","level":1,"time":"2025-11-19T17:21:27+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\\OC\\Updater::dbUpgradeBefore: Updating database schema","userAgent":"--","version":"31.0.10.2","data":{"app":"updater"}}
[...]
{"reqId":"fdq97DOQSkL4rmGMvdQ0","level":0,"time":"2025-11-19T17:21:46+00:00","remoteAddr":"","user":"--","app":"serverDI","method":"","url":"--","message":"The requested alias \"IntegrityCodeChecker\" is deprecated. Please request \"OC\\IntegrityCheck\\Checker\" directly. This alias will be removed in a future Nextcloud version.","userAgent":"--","version":"31.0.10.2","data":{"app":"serverDI"}}
{"reqId":"fdq97DOQSkL4rmGMvdQ0","level":1,"time":"2025-11-19T17:21:46+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\\OC\\Updater::startCheckCodeIntegrity: Starting code integrity check...","userAgent":"--","version":"31.0.10.2","data":{"app":"updater"}}
{"reqId":"fdq97DOQSkL4rmGMvdQ0","level":1,"time":"2025-11-19T17:21:53+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\\OC\\Updater::finishedCheckCodeIntegrity: Finished code integrity check","userAgent":"--","version":"31.0.10.2","data":{"app":"updater"}}
{"reqId":"fdq97DOQSkL4rmGMvdQ0","level":1,"time":"2025-11-19T17:21:53+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\\OC\\Updater::updateEnd: Update successful","userAgent":"--","version":"32.0.1.2","data":{"app":"updater"}}
{"reqId":"fdq97DOQSkL4rmGMvdQ0","level":1,"time":"2025-11-19T17:21:53+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\\OC\\Updater::maintenanceActive: Maintenance mode is kept active","userAgent":"--","version":"32.0.1.2","data":{"app":"updater"}}
{"reqId":"fdq97DOQSkL4rmGMvdQ0","level":1,"time":"2025-11-19T17:21:53+00:00","remoteAddr":"","user":"--","app":"updater","method":"","url":"--","message":"\\OC\\Updater::resetLogLevel: Reset log level to Warning(2)","userAgent":"--","version":"32.0.1.2","data":{"app":"updater"}}

Web Browser

The problem is not related to the Web interface.

Web server / Reverse Proxy

Nginx is not the problem here. The server can be reached.

Configuration

Nextcloud

The output of occ config:list system or similar is best.

However, I can’t get it from occ-docker, because I get this error (which I expect): Error response from daemon: No such container: nextcloud-aio-nextcloud.

Apps

The output of occ app:list (if possible).

See above.

I’m sorry, I’m stupid. I found the solution myself, and it actually had to do with certificates. I did something wrong when I installed my self-signed CA, and I haven’t been able to use other CAs since: being unable to docker pull ghcr.io/nextcloud-releases/all-in-one was the giveaway. Disinstalling and re-installing ca-certificates, then registering my CA again worked. After that, I could update the master container and everything worked again.

1 Like

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.