Incomplete container startup during AIO upgrade (v12.9.2 → v13.0.0 Beta)

[vawaver]

Describe the bug

During upgrade from AIO v12.9.2 (stable) to v13.0.0 Beta, the update process does not start all required containers.

This happened after switching the AIO channel to Beta via docker-compose.yml.

This is the first time this behavior occurred. Previous updates worked without any issues.

The issue appears identical to the one described here:
https://help.nextcloud.com/t/aio-mastercontainer-doesnt-start-all-nextcloud-containers/243815

---

Steps to reproduce

1. Run Nextcloud AIO v12.9.2 (stable)
2. Stop the AIO mastercontainer
3. Change the AIO image/channel to Beta in docker-compose.yml
4. Recreate/start the AIO mastercontainer v13.0.0 Beta
5. Open the AIO interface v13.0.0 Beta
6. Click "Start and update containers"
7. Observe that not all containers are started / created

---

Expected behavior

All required containers should be created and started automatically after triggering the update.

---

Actual behavior

• Update process does not properly start all containers
• Some containers are missing / not created
• System remains in incomplete state

---

Environment

• Nextcloud AIO: v12.9.2 → v13.0.0 Beta
• Reverse proxy: Nginx Proxy Manager 2.14.0
• Deployment: Docker (docker-compose)
• Setup: long-term stable configuration, no recent changes

---

Additional context

• This setup has been running unchanged for a long time
• Reverse proxy configuration has not been modified
• No infrastructure or system-level changes were made before the update
• Issue occurred immediately after switching to Beta and triggering the update

This suggests the problem is likely related to the upgrade process itself rather than environment changes.

---

Possible hint

Based on the forum discussion, this could be related to how the AIO interface is accessed via reverse proxy, potentially affecting internal requests triggered during the update process.