← All apps

Nextcloud AIO

AIO manages Nextcloud, its database, backups and companion containers. Connect a TLS reverse proxy to the local Apache port after completing AIO setup.

Choose your deployment and the way you want to use Selfhost. The instructions below follow that choice.

Deployment Nextcloud AIOUse Selfhost with Standalone CLIDashboard

Set up Nextcloud AIO

AIO manages Nextcloud, its database, backups and companion containers. Connect a TLS reverse proxy to the local Apache port after completing AIO setup.

Customize deployment inputs (2)

Local AIO administration HTTPS port port

portDefault: 18081

Local Apache port for your reverse proxy apache-port

portDefault: 11000

Review this deployment’s requirements

Allow the AIO manager to control this server's Docker engine. This provides root-equivalent access despite the read-only socket mount.Use an engine with no existing AIO manager or master volume. AIO requires fixed names and one manager per engine.Use AIO for app installation, backups and upgrades. Selfhost manages only the AIO administration container.

Your selections add the matching CLI acknowledgements. The installer checks them again.

Save this as inputs.json and adjust the values before initialization.

{
  "port": 18081,
  "apache-port": 11000
}

Review and acknowledge every requirement above before running initialization.

selfhost app --directory ./nextcloud-aio init nextcloud-aio --stack --inputs inputs.json

Initialization writes portable files and does not start the app. Review compose.yaml, the private .env and any files in files/, then start it:

selfhost app --directory ./nextcloud-aio start

No Selfhost dashboard or background service is needed. You can also start these files directly:

cd nextcloud-aio
docker compose -f compose.yaml up -d

• Review the project configuration, then start the AIO manager. The Docker socket must exist on the selected engine host.
• Open https://localhost:18081 using the administration port you chose. For a remote server, use an SSH port forward. AIO uses its own self-signed administration certificate.
• Complete AIO setup with your Nextcloud domain. Use a TLS reverse proxy on the same server connected to the Apache port, or a private tunnel from a remote proxy.
• Use AIO to start, update and back up its Nextcloud stack. Stopping this Selfhost project stops only the AIO manager, not AIO's child containers.
• Once Nextcloud is running, link its app container under Existing apps for status and optional management actions.

Connect an existing installation

Use Existing apps → Link an app in the dashboard, or the CLI’s existing-app commands. Choose Nextcloud AIO, its URL and, optionally, its exact Docker container on a connected server.

Save existing.json with your app URL. Add server_id and container for container inspection and actions.

{
  "profile": "nextcloud-aio",
  "name": "Nextcloud AIO",
  "url": "https://app.example.com"
}

selfhost existing link --file existing.json
selfhost existing list
selfhost existing inspect EXISTING_ID

Linking enables the existing-app profile’s supported inspection and actions. It does not import Compose or attach the new-deployment settings and onboarding profiles described below.

Existing app commands, permissions and unlinking

Actions for a linked container

Nextcloud status

Read version, installation and maintenance status.

selfhost existing action EXISTING_ID status

Installed apps

List enabled and disabled Nextcloud apps.

selfhost existing action EXISTING_ID apps

Update Nextcloud apps

Update all installed Nextcloud apps. Create an AIO backup first. Core and container upgrades stay in AIO.

Enable this action explicitly in management permissions on a writable server. Running it also requires the exact saved app name.

selfhost existing action EXISTING_ID update-apps --confirm "EXACT_APP_NAME"

Run maintenance repair

Run Nextcloud maintenance repair. Create and verify a backup before proceeding.

Enable this action explicitly in management permissions on a writable server. Running it also requires the exact saved app name.

selfhost existing action EXISTING_ID repair --confirm "EXACT_APP_NAME"

Integrations for this deployment

This deployment has no attached native settings or onboarding profile. Follow its setup instructions above and use the app’s own administration interface. Choosing another deployment can expose different Selfhost integrations.

Versions and updates

This deployment uses the following images. Existing projects retain their saved recipe and images. A new catalogue version does not silently update them.

• aio: ghcr.io/nextcloud-releases/all-in-one:latest

Review compatibility and back up app data before an update. Choose an image version and review the change.

Keep control of your setup

Selfhost remains optional. Your app runs using ordinary Compose files, its own settings and persistent data. Keep the Compose project name and volumes to preserve storage. Configuration exports and setting backups do not include application data.

Standalone CLI guide · Backups and removal