Mastercontainer update failed.

ℹ️ Support
, , ,
1
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):
    • probably 32.0.2
  • Operating system and version (e.g., Ubuntu 24.04):
    • Rocky Linux 9.7
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • AIO
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • no
volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer

networks:
  nextcloud-aio:
    external: true

services:

  nginx_proxy_manager:
    image: jc21/nginx-proxy-manager:latest
    restart: unless-stopped
    container_name: nginx_proxy_manager
    ports:
      - 80:80
      - 443:443
    expose:
      - 81:81
    networks:
      - nextcloud-aio
    volumes:
      - ./nginx_proxy_manager/data:/data
      - ./nginx_proxy_manager/letsencrypt:/etc/letsencrypt

  nextcloud:
    image: nextcloud/all-in-one:latest
    restart: unless-stopped
    container_name: nextcloud-aio-mastercontainer
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /run/user/1000/docker.sock:/var/run/docker.sock:ro
    # ports:
    expose:
      - 8080:8080
    networks:
      - nextcloud-aio
    environment:
      - APACHE_PORT=11000
      - WATCHTOWER_DOCKER_SOCKET_PATH=/run/user/1000/docker.sock
    depends_on:
      - nginx_proxy_manager

Summary of the issue you are facing:

I tried to do a mastercontainer update. I firstly update system package by sudo dnf update and then it failed to start. So I check some methods.

I first notice:

strconv.ParseUint: parsing "81:81": invalid syntax

then I tried search solutions

They says

docker system prune -f

not working, then I checked logs, found related issues on github

so I followed this: Breaks with Docker v29 due to Docker API Version <v1.44 · Issue #698 · nextcloud/app_api · GitHub

The mastercontainer successfully updated, but it now asked me set domain as first installation.

During the time, I tried rebuild nextcloud-aio network too.

https://github.com/nextcloud/all-in-one/discussions/4989

Even worse, after reboot system, this shows again

strconv.ParseUint: parsing "81:81": invalid syntax

when try to do docker compose up

2

From what I can see, your current setup mixes Nginx Proxy Manager and the entire Nextcloud AIO stack inside one shared Docker Compose environment. This is the main reason why your update failed and why AIO behaved as if it were a fresh installation.

In my deployment guide here:
https://help.nextcloud.com/t/proxmox-nginx-nextcloud-aio-watchtower-deployment-guide/233643
I explain a structure where Nginx Proxy Manager and Nextcloud AIO run separately.
The guide uses two VMs for clarity, but the same principle works even if both services run side-by-side on the same host.

The key point is to keep them logically separated:

  • NPM has its own clean docker-compose.yml and only exposes ports 80 / 81 / 443.

  • Nextcloud AIO has its own compose, its own network, and its own volumes.

  • No shared compose file and no shared networks between them.

This separation gives you two benefits:

  1. Safe updates:
    NPM can be updated with Watchtower, while AIO uses its built-in updater without interference.

  2. Simpler troubleshooting:
    A small misconfiguration in NPM (such as expose: 81:81) cannot break the entire AIO stack.

If you follow the separation model from the guide, NPM will run perfectly alongside Nextcloud AIO, and problems like this will not occur.