Nextcloud All-in-One

> [!NOTE]
> Nextcloud AIO is actively looking for contributors. See the forum post.

The official Nextcloud installation method. Nextcloud AIO provides easy deployment and maintenance with most features included in this one Nextcloud instance.

Included are:

• Nextcloud
• High performance backend for Nextcloud Files (Client Push)
• Redis & APCU for performant caching
• PostgreSQL as database
• Nextcloud Office (optional)
• EuroOffice (optional)
• High performance backend for Nextcloud Talk and TURN-server (optional)
• Nextcloud Talk Recording-server (optional)
• Backup solution (optional, based on BorgBackup)
• Imaginary (optional, for previews of heic, heif, illustrator, pdf, svg, tiff and webp)
• ClamAV (optional, Antivirus backend for Nextcloud)
• Fulltextsearch (optional)
• Whiteboard (optional)
• Docker Socket Proxy (optional, needed for Nextcloud App API)
• Community containers

And much more:

• Simple web interface included that enables easy installation and maintenance
• Easy updates included
• Update and backup notifications included
• Daily backups can be enabled from the AIO interface which also allows updating all containers, Nextcloud and its apps afterwards automatically
• Instance restore from backup archive via the AIO interface included (you only need the archive and the password in order to restore the whole instance on a new AIO instance)
• APCu as local cache
• Redis as distributed cache and for file locking
• Postgresql as database
• PHP-FPM with performance-optimized config (e.g. Opcache and JIT enabled by default)
• A+ security in Nextcloud security scan
• Ready to be used behind existing Reverse proxies
• Can be used behind Cloudflare Tunnel
• Can be used via Tailscale
• Ready for big file uploads up to 10 GB on public links, adjustable (logged in users can upload much bigger files using the webinterface or the mobile/desktop clients since chunking is used in that case)
• PHP and web server timeouts set to 3600s, adjustable (important for big file uploads)
• Defaults to a max of 512 MB RAM per PHP process, adjustable
• Automatic TLS included (by using Let's Encrypt)
• Brotli compression enabled by default for javascript, css and svg files which reduces Nextcloud load times
• HTTP/2 and HTTP/3 enabled
• "Pretty URLs" for Nextcloud are enabled by default (removes the index.php from all links)
• Video previews work out of the box and when Imaginary is enabled, many recent image formats as well!
• Only one domain and not multiple domains are required for everything to work (usually you would need to have one domain for each service which is much more complex)
• Adjustable location of Nextcloud's datadir (e.g. good for easy file-sharing with host system on Windows and MacOS)
• By default confined (good for security) but can allow access to additional storages in order to enable the usage of the local external storage feature
• Possibility included to adjust default installed Nextcloud apps
• Nextcloud installation is not read only - that means you can apply patches if you should need them (instead of having to wait for the next release for them getting applied)
• ffmpeg, smbclient and nodejs are included by default
• Possibility included to permanently add additional OS packages into the Nextcloud container without having to build your own Docker image
• Possibility included to permanently add additional PHP extensions into the Nextcloud container without having to build your own Docker image
• Possibility included to pass the needed device for hardware transcoding to the Nextcloud container
• Possibility included to store all docker related files on a separate drive
• LDAP can be used as user backend for Nextcloud
• Migration from any former Nextcloud installation to AIO is possible. See this documentation.
• Migration in the other direction (e.g. from AIO to a VM-based installation) is also possible.
• Fail2Ban can be added
• phpMyAdmin, Adminer or pgAdmin can be added
• Mail server can be added
• Nextcloud can be accessed locally via the domain
• Can be installed locally (if you don't want or cannot make the instance publicly reachable)
• Free deSEC dynamic-DNS domain (*.dedyn.io) can be registered directly from the AIO interface — no external domain needed
• IPv6-ready
• Can be used with Docker rootless (good for additional security)
• Runs on all platforms Docker supports (e.g. also on Windows and Macos)
• Included containers easy to debug by having the possibility to check their logs directly from the AIO interface
• Docker-compose ready
• Can be installed without a container having access to the docker socket
• Can be installed with Docker Swarm
• Can be installed with Kubernetes
• Almost all included containers Alpine Linux based (good for security and size)
• Many of the included containers run as non-root user (good for security)
• Many of the included containers have a read-only root-FS (good for security)
• Included containers run in its own docker network (good for security) and only really necessary ports are exposed on the host
• Multiple instances on one server are doable without having to deal with VMs
• Adjustable backup path or remote borg repository from the AIO interface (good to put the backups e.g. on a different drive if using a local backup path)
• Possibility included to also back up external Docker Volumes or Host paths (can be used for host backups)
• Borg backup can be completely managed from the AIO interface, including backup creation, backup restore, backup integrity check and integrity-repair
• Other forms of remote backup are indirectly possible
• Updates and backups can be run from an external script. See this documentation for a complete example.

Screenshots

| First setup | After installation |
|---|---|
| !image | !image |

Architecture overview

flowchart TB
    %% ── Styles ───────────────────────────────────────────────────────────────────
    classDef user      fill:#FFF3CD,stroke:#F0AD4E,color:#333
    classDef master    fill:#E8D5F5,stroke:#9B59B6,color:#222
    classDef core      fill:#D6EAF8,stroke:#2E86C1,color:#222
    classDef opt       fill:#D5F5E3,stroke:#27AE60,color:#222
    classDef community fill:#FDEBD0,stroke:#E67E22,color:#222
    classDef access    fill:#EAFAF1,stroke:#1E8449,color:#222

    %% ── Top row: people ─────────────────────────────────────────────────────────
    YOU(["🧑‍💻 Adminn(You)"]):::user
    ENDUSER(["🧑‍🤝‍🧑 Usersn(family / team)"]):::user

    %% ── Everything that runs inside AIO ─────────────────────────────────────────
    subgraph AIO["  🐳  Nextcloud AIO  "]
        MC(["🧠 Mastercontainern─────────────────────────n▸ AIO interface :8080 / :8443n▸ Manages & updates containersn▸ Handles backups"]):::master

        subgraph CORE["  📦  Core Stack  (auto-started)  "]
            PROXY(["🔀 ApachenProxy & HTTPS"]):::core
            NC(["☁️ NextcloudnApp Server"]):::core
            DB(["🗄️ PostgreSQLnDatabase"]):::core
            CACHE(["⚡ RedisnCache"]):::core
            PUSH(["🔔 Notify PushnReal-time sync"]):::core
        end

        subgraph OPT["  🧩  Optional Built-in Containers  (enable in AIO interface)  "]
            COLLA(["📄 Nextcloud Office"]):::opt
            EO(["📄 EuroOfficenDocument Server"]):::opt
            TALK(["🎙️ TalknVideo & Voice calls"]):::opt
            TALKREC(["🎬 Talk Recording"]):::opt
            FTS(["🔎 Full-text Searchn(Elasticsearch)"]):::opt
            IMAG(["🖼️ ImaginarynImage previews"]):::opt
            CLAM(["🦠 ClamAVnAntivirus"]):::opt
            WB(["🖊️ Whiteboard"]):::opt
        end

        COMM(["🌍 Community Containersn──────────────────────n30+ optional add-onsnSee community-containers/"]):::community
        click COMM "https://github.com/nextcloud/all-in-one/tree/main/community-containers#community-containers" "Browse community containers"
    end

    %% ── Result node (outside AIO) ────────────────────────────────────────────────
    NC_URL(["🌐 https://your-domain.comn✅ Nextcloud — ready to use!"]):::access

    %% ── Flows ────────────────────────────────────────────────────────────────────
    YOU -->|"① open :8080 or :8443 in browser"| MC
    MC -->|"② auto-starts & wires up"| CORE
    MC -. "③ enable in AIO interface" .-> OPT
    MC -. "④ add via AIO interface" .-> COMM

    PROXY --> NC
    NC --- DB
    NC --- CACHE
    NC --- PUSH
    OPT -->|"integrate with"| NC
    COMM -.->|"integrate with"| NC

    CORE -->|"⑤ stack is ready!"| NC_URL
    ENDUSER -->|"⑥ browser / app"| NC_URL
    YOU -->|"⑥ use normally"| NC_URL

How to use this?

The steps below are written for Linux. For platform-specific guidance see:

• macOS: How to run AIO on macOS?
• Windows: How to run AIO on Windows?
• Unraid: How to run AIO on Unraid?
• Synology DSM: How to run AIO on Synology DSM?
• TrueNAS SCALE: Can I run AIO on TrueNAS SCALE?

> [!IMPORTANT]
> These instructions assume there is no existing web server or reverse proxy (for example Apache, Nginx, Caddy, or Cloudflare Tunnel) that you intend to place in front of AIO. If you plan to run AIO behind an existing web server or reverse proxy, follow the AIO reverse proxy documentation: Reverse proxy docs

You're encouraged to skim the attached FAQ. While we've tried to make things straightforward, Nextcloud is a large and flexible platform. Reading the FAQ will save you time, particularly if edge cases come up.

> [!TIP]
> Don't worry about getting everything perfect on the first try — test deployments are cheap and disposable.

1. Install Docker on your Linux host by following the official documentation: Docker install — supported platforms

> [!WARNING]
> Snap-based Docker installations are not supported. Make sure you are not using a snap-based Docker installation (generally only applicable to Ubuntu). To check, run:
>

> sudo docker info | grep "Docker Root Dir" | grep "/var/snap/docker/"
>

> If you see the following output:
>

> /var/snap/docker/
>

> you should migrate to a standard Docker installation and remove the snap-based package before proceeding: Install Docker on Ubuntu.
>
> ⚠️ To avoid losing data or interrupting services, only remove the Docker snap after you are certain you're not running any existing containers in it.
>
> Consult the official Docker documentation or other guides for instructions on migrating existing containers. Once you are certain it's safe, remove the snap-based Docker installation with:
>

> sudo snap remove docker
>

1. If you need IPv6 support, enable it by following: Docker IPv6 support for AIO

1. AIO uses a special mastercontainer to orchestrate the various pieces of the Nextcloud stack. To start AIO, launch the mastercontainer with the command below:

# For Linux and without a web server or reverse proxy already in place:
sudo docker run 
  --init 
  --sig-proxy=false 
  --name nextcloud-aio-mastercontainer 
  --restart always 
  --publish 80:80 
  --publish 8080:8080 
  --publish 8443:8443 
  --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config 
  --volume /var/run/docker.sock:/var/run/docker.sock:ro 
  ghcr.io/nextcloud-releases/all-in-one:latest

Explanation of the command

• sudo docker run — starts a new Docker container. Omit sudo if your user is in the docker group.
• --init — runs an init process inside the container to handle zombie processes.
• --sig-proxy=false — prevents Ctrl+C in the attached terminal from stopping the container.
• --name nextcloud-aio-mastercontainer — the container name. Do not change this name; mastercontainer updates rely on it.
• --restart always — ensures the container restarts automatically with the Docker daemon.
• --publish 80:80 — publishes container port 80 on host port 80 (used for ACME http-challenge when obtaining certificates, used for for the AIO-interface running inside the mastercontainer). Not required if you run AIO behind a reverse proxy.
• --publish 8080:8080 — publishes the AIO interface (self-signed certificate) on host port 8080. You may map a different host port if 8080 is in use (e.g. --publish 8081:8080).
• --publish 8443:8443 — publishes the AIO interface with a valid certificate on host port 8443 (requires ports 80 and 8443 to be reachable and a domain pointing to your server). Not required if you run AIO behind a reverse proxy.
• --volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config — stores mastercontainer configuration in the named Docker volume. Do not change this volume name; built-in backups depend on it.
• --volume /var/run/docker.sock:/var/run/docker.sock:ro — mounts the Docker socket (read-only) so the mastercontainer can manage other containers. On Windows/macOS or when using rootless Docker, this path may need adjustment; see the platform-specific docs. If you change the socket path, also set WATCHTOWER_DOCKER_SOCKET_PATH accordingly. If you prefer not to expose the socket, see the manual-install documentation: Manual install without docker socket access
• ghcr.io/nextcloud-releases/all-in-one:latest — the mastercontainer image.

Additional options can be set with environment variables (for example --env NEXTCLOUD_DATADIR="/mnt/ncdata" to change Nextcloud's datadir on first startup). See the Customization section and example compose file: compose.yaml for more options.

> [!TIP]
> If you want Nextcloud’s data directory in a different location than the default Docker volume, see "How to change the default location of Nextcloud's Datadir" in this README: How to change the default location of Nextcloud's Datadir

> [!NOTE]
> For production usage (and ease of upgrades and changes), we suggest using the example Compose file rather than docker run.

1. After the initial startup, open the Nextcloud AIO interface on port 8080 of this server by IP address, for example:

https://192.168.5.5:8080

> [!CAUTION]
> Use an IP address (not a domain) when accessing the AIO interface on port 8080. Accessing via a domain may work temporarily but is likely to break later due to HSTS.

Port 8080 uses a self-signed certificate that you must accept in your browser.

It is also possible to obtain a valid certificate automatically if your firewall/router forwards ports 80 and 8443 and you point a domain to your server. In that case, access the AIO interface using the dedicated port for this purpose (8443), for example:

https://your-domain-that-points-to-this-server.tld:8443

1. If you enable Nextcloud Talk, open port 3478/TCP and 3478/UDP in your firewall/router for the Talk (TURN) container.

> [!TIP]
> Don't have a domain yet? AIO can register a free dynamic-DNS subdomain under dedyn.io for you via deSEC — no external setup needed. Look for the "Don't have a domain? Get a free one from deSEC" section on the AIO interface when you are asked to enter your domain. AIO will automatically register the domain, keep the DNS record up to date, and enable the Caddy community container as a reverse proxy as well as the dnsmasq container for local DNS resolution.

FAQ

• TOC
• Where can I find additional documentation?
• How does it work?
• How to contribute?
• How many users are possible?
• Network
• Are reverse proxies supported?
• Which ports are mandatory to be open in your firewall/router?
• Explanation of used ports
• Notes on Cloudflare (proxy/tunnel)
• How to run Nextcloud behind a Cloudflare Tunnel?
• How to run Nextcloud via Tailscale?
• How to get a free domain via deSEC?
• How to get Nextcloud running using the ACME DNS-challenge?
• How to run Nextcloud locally? No domain wanted, or wanting intranet access within your LAN.
• Can I use an ip-address for Nextcloud instead of a domain?
• Can I run AIO offline or in an airgapped system?
• Are self-signed certificates supported for Nextcloud?
• Can I use AIO with multiple domains?
• Are other ports than the default 443 for Nextcloud supported?
• Can I run Nextcloud in a subdirectory on my domain?
• How can I access Nextcloud locally?
• How to overwrite the local DNS resolution for some domains or add extra hosts to the containers?
• How to skip the domain validation?
• How to resolve firewall problems with Fedora Linux, RHEL OS, CentOS, SUSE Linux and others?
• What can I do to fix the internal or reserved ip-address error?
• How to adjust the MTU size of the docker network
• Infrastructure
• Which CPU architectures are supported?
• Disrecommended VPS providers
• Recommended VPS
• Note on storage options
• Are there known problems when SELinux is enabled?
• Customization
• How to adjust the internally used docker api version?
• How to adjust the log level for AIO components?
• How to change the default location of Nextcloud's Datadir?
• How to configure custom UID/GID?
• How to move the appdata folder from the datadir to an ssd to improve the performance?
• How to store the files/installation on a separate drive?
• How to limit the resource usage of AIO?
• How to allow the Nextcloud container to access directories on the host?
• How to adjust the Talk port?
• How to adjust the upload limit for Nextcloud?
• How to adjust the max execution time for Nextcloud?
• How to adjust the PHP memory limit for Nextcloud?
• How to change the Nextcloud apps that are installed on the first startup?
• How to add OS packages permanently to the Nextcloud container?
• How to add PHP extensions permanently to the Nextcloud container?
• What about the pdlib PHP extension for the facerecognition app?
• How to enable hardware acceleration for Nextcloud?
• With open source drivers MESA for AMD, Intel and new drivers <code class="ra0-md-code">Nouveau</code> for Nvidia
• With proprietary drivers for Nvidia :warning: BETA
• How to keep disabled apps?
• How to trust user-defined Certification Authorities (CA)?
• How to disable Collabora's Seccomp feature?
• How to adjust the Fulltextsearch Java options?
• Guides
• How to run AIO on macOS?
• How to run AIO on Windows?
• How to run AIO on Unraid?
• How to run AIO on Synology DSM
• How to run AIO with Portainer?
• Can I run AIO on TrueNAS SCALE?
• How to run <code class="ra0-md-code">occ</code> commands?
• How to resolve <code class="ra0-md-code">Security & setup warnings displays the "missing default phone region" after initial install</code>?
• How to run multiple AIO instances on one server?
• Bruteforce protection FAQ
• How to switch the channel?
• How to update the containers?
• How to easily log in to the AIO interface?
• How to change the domain?
• How to properly reset the instance?
• Can I use a CIFS/SMB share as Nextcloud's datadir?
• Can I run this with Docker swarm?
• Can I run this with Kubernetes?
• How to run this with Docker rootless?
• Can I run this with Podman instead of Docker?
• Access/Edit Nextcloud files/folders manually
• How to edit Nextclouds config.php file with a texteditor?
• How to change default files by creating a custom skeleton directory?
• How to adjust the version retention policy and trashbin retention policy?
• How to enable automatic updates without creating a backup beforehand?
• Securing the AIO interface from unauthorized ACME challenges
• How to migrate from an already existing Nextcloud installation to Nextcloud AIO?
• Backup
• What is getting backed up by AIO's backup solution?
• How to adjust borgs retention policy?
• How to migrate from AIO to AIO?
• Are remote borg backups supported?
• Failure of the backup container in LXC containers
• How to create the backup volume on Windows?
• Pro-tip: Backup archives access
• Delete backup archives manually
• Sync local backups regularly to another drive
• How to exclude Nextcloud's data directory or the preview folder from backup?
• How to stop/start/update containers or trigger the daily backup from a script externally?
• How to disable the backup section?
• Addons
• Fail2ban
• LDAP
• Netdata
• USER_SQL
• phpMyAdmin, Adminer or pgAdmin
• Mail server
• Miscellaneous
• Requirements for integrating new containers
• AIO release policy
• Nextcloud update policy
• How often are update notifications sent?
• Huge docker logs

Where can I find additional documentation?

Some of the documentation is available on GitHub Discussions.

How does it work?

Nextcloud AIO is inspired by projects like Portainer that manage the docker daemon by talking to it through the docker socket directly. This concept allows a user to install only one container with a single command that does the heavy lifting of creating and managing all containers that are needed in order to provide a Nextcloud installation with most features included. It also makes updating a breeze and is not bound to the host system (and its slow updates) anymore as everything is in containers. Additionally, it is very easy to handle from a user perspective because a simple interface for managing your Nextcloud AIO installation is provided.

How to contribute?

See this issue for a list of feature requests that need help by contributors.

How many users are possible?

Up to 100 users are free, more are possible with Nextcloud Enterprise

Network

Are reverse proxies supported?

Yes. Please refer to the following documentation on this: reverse-proxy.md

Which ports are mandatory to be open in your firewall/router?

Only those (if you access the Mastercontainer Interface internally via port 8080):

• 443/TCP for the Apache container
• 443/UDP if you want to enable http3 for the Apache container
• 3478/TCP and 3478/UDP for the Talk container

Explanation of used ports

• 8080/TCP: Mastercontainer Interface with self-signed certificate (works always, also if only access via IP-address is possible, e.g. https://ip.address.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! (It is also expected that this port uses a self-signed certificate due to security concerns which you need to accept in your browser)
• 80/TCP: redirects to Nextcloud (is used for getting the certificate via ACME http-challenge for the Mastercontainer)
• 8443/TCP: Mastercontainer Interface with valid certificate (only works if port 80 and 8443 are open/forwarded in your firewall/router and you point a domain to your server. It generates a valid certificate then automatically and access via e.g. https://public.domain.com:8443/ is possible.)
• 443/TCP: will be used by the Apache container later on and needs to be open/forwarded in your firewall/router
• 443/UDP: will be used by the Apache container later on and needs to be open/forwarded in your firewall/router if you want to enable http3
• 3478/TCP and 3478/UDP: will be used by the Turnserver inside the Talk container and needs to be open/forwarded in your firewall/router

Notes on Cloudflare (proxy/tunnel)

Since Cloudflare Proxy/Tunnel comes with a lot of limitations which are listed below, it is rather recommended to use the built-in deSEC domain registration or switch to Tailscale if possible.

• Cloudflare Proxy and Cloudflare Tunnel both require Cloudflare to perform TLS termination on their side and thus decrypt all the traffic on their infrastructure. This is a privacy concern and you will need to look for other solutions if it's unacceptable for you.
• Using Cloudflare Tunnel might potentially slow down Nextcloud since local access via the configured domain is not possible because TLS termination is in that case offloaded to Cloudflare's infrastructure. There is no way to disable this behavior in Cloudflare Tunnel.
• It is known that the domain validation may not work correctly behind Cloudflare since Cloudflare might block the validation attempt. You can simply skip it in that case by following: https://github.com/nextcloud/all-in-one#how-to-skip-the-domain-validation
• Make sure to disable Cloudflares Rocket Loader feature as otherwise Nextcloud's login prompt will not be shown.
• Cloudflare only supports uploading files up to 100 MB in the free plan, if you try to upload bigger files you will get an error (413 - Payload Too Large) if no chunking is used (e.g. for public uploads in the web, or if chunks are configured to be bigger than 100 MB in the clients or the web). If you need to upload bigger files, you need to disable the proxy option in your DNS settings. Note that this will both disable Cloudflare DDoS protection and Cloudflare Tunnel as these services require the proxy option to be enabled.
• If using Cloudflare Tunnel and the Nextcloud Desktop Client Set Chunking on Nextcloud Desktop Client
• Cloudflare only allows a max timeout of 100s for requests which is not configurable. This means that any server-side processing e.g. for assembling chunks for big files during upload that take longer than 100s will simply not work. See https://github.com/nextcloud/server/issues/19223. If you need to upload big files reliably, you need to disable the proxy option in your DNS settings. Note that this will both disable Cloudflare DDoS protection and Cloudflare Tunnel as these services require the proxy option to be enabled.
• It is known that the in AIO included collabora (Nextcloud Office) does not work out of the box behind Cloudflare. To make it work, you need to add all Cloudflare IP-ranges to the wopi-allowlist in https://yourdomain.com/settings/admin/richdocuments
• Cloudflare Proxy might block the Turnserver for Nextcloud Talk from working correctly. You might want to disable Cloudflare Proxy thus. See https://github.com/nextcloud/all-in-one/discussions/2463#discussioncomment-5779981
• The built-in turn-server for Nextcloud Talk will not work behind Cloudflare Tunnel since it needs a separate port (by default 3478 or as chosen) available on the same domain. If you still want to use the feature, you will need to install your own turnserver or use a publicly available one and adjust and test your stun and turn settings in https://yourdomain.com/settings/admin/talk.
• If you get an error in Nextcloud's admin overview that the HSTS header is not set correctly, you might need to enable it in Cloudflare manually.
• If you are using AIO's built-in Reverse Proxy and don't use your own, then the certificate issuing may possibly not work out-of-the-box because Cloudflare might block the attempt. In that case you need to disable the Proxy feature at least temporarily in order to make it work. Note that this isn't an option if you need Cloudflare Tunnel as disabling the proxy would also disable Cloudflare Tunnel which would in turn make your server unreachable for the verification. See https://github.com/nextcloud/all-in-one/discussions/1101.

How to run Nextcloud behind a Cloudflare Tunnel?

Although it does not seems like it is the case but from AIO perspective a Cloudflare Tunnel works like a reverse proxy. So please follow the reverse proxy documentation where is documented how to make it run behind a Cloudflare Tunnel. However please see the caveats before proceeding.

How to run Nextcloud via Tailscale?

For a reverse proxy example guide for Tailscale, see this guide by @Perseus333: https://github.com/nextcloud/all-in-one/discussions/6817

How to get a free domain via deSEC?

deSEC offers free dynamic-DNS subdomains under dedyn.io. AIO integrates the registration process directly:

1. Open the AIO interface and expand the "Don't have a domain? Get a free one from deSEC" section on the domain-entry page.
2. Enter your email address and, optionally, a desired subdomain slug (the part before .dedyn.io). Leave the slug blank for a random one.
3. Click Register free domain via deSEC. AIO will create a deSEC account, register the subdomain and store the credentials in its configuration.

After successful registration:

• AIO sets the registered *.dedyn.io domain as the Nextcloud domain automatically.
• The Caddy community container is enabled as a reverse proxy.
• The dnsmasq community container is enabled so that LAN devices can resolve the domain to the server's local IP. Follow the dnsmasq documentation for the required router change.
• The mastercontainer keeps the DNS record up to date automatically when your public IP changes.

How to get Nextcloud running using the ACME DNS-challenge?

You can install AIO behind an external reverse proxy where is also documented how to get it running using the ACME DNS-challenge for getting a valid certificate for AIO. See the reverse proxy documentation. (Meant is the Caddy with ACME DNS-challenge section). Also see https://github.com/dani-garcia/vaultwarden/wiki/Running-a-private-vaultwarden-instance-with-Let%27s-Encrypt-certs#getting-a-custom-caddy-build for additional docs on this topic.

How to run Nextcloud locally? No domain wanted, or wanting intranet access within your LAN.

If you do not want to open Nextcloud to the public internet, you may have a look at the following documentation on how to set it up locally: local-instance.md, but keep in mind you're still required to have https working properly.

Can I use an ip-address for Nextcloud instead of a domain?

No and it will not be added. If you only want to run it locally, you may have a look at the following documentation: local-instance.md. Recommended is to use the built-in deSEC domain registration to get a free domain automatically, or alternatively Tailscale.

Can I run AIO offline or in an airgapped system?

No. This is not possible and will not be added due to multiple reasons: update checks, app installs via app-store, downloading additional docker images on demand and more.

Are self-signed certificates supported for Nextcloud?

No and they will not be. If you want to run it locally, without opening Nextcloud to the public internet, please have a look at the local instance documentation. Recommended is to use the built-in deSEC domain registration to obtain a free domain with a valid certificate automatically, or alternatively Tailscale.

Can I use AIO with multiple domains?

No and it will not be added. However you can use this feature in order to create multiple AIO instances, one for each domain.

Are other ports than the default 443 for Nextcloud supported?

No and they will not be. If port 443 and/or 80 is blocked for you, you may use the built-in deSEC domain registration (which uses the Caddy community container on port 443) or Tailscale if you want to publish it online. If you already run a different service on port 443, please use a dedicated domain for Nextcloud and set it up correctly by following the reverse proxy documentation. However in all cases the Nextcloud interface will redirect you to port 443.

Can I run Nextcloud in a subdirectory on my domain?

No and it will not be added. Please use a dedicated (sub-)domain for Nextcloud and set it up correctly by following the reverse proxy documentation. If you don't have a domain yet, use the built-in deSEC domain registration to get one for free, or alternatively Tailscale.

How can I access Nextcloud locally?

Please note that local access is not possible if you are running AIO behind Cloudflare Tunnel since TLS proxying is in that case offloaded to Cloudflares infrastructure. You can fix this by setting up your own reverse proxy that handles TLS proxying locally and will make the steps below work.

Please make sure that if you are running AIO behind a reverse proxy, that the reverse proxy is configured to use port 443 on the server that runs it. Otherwise the steps below will not work.

Now that this is out of the way, the recommended way how to access Nextcloud locally, is to set up a local dns-server like a pi-hole and set up a custom dns-record for that domain that points to the internal ip-adddress of your server that runs Nextcloud AIO. Below are some guides:

• https://www.howtogeek.com/devops/how-to-run-your-own-dns-server-on-your-local-network/
• https://help.nextcloud.com/t/need-help-to-configure-internal-access/156075/6
• https://howchoo.com/pi/pi-hole-setup together with https://web.archive.org/web/20221203223505/https://docs.callitkarma.me/posts/PiHole-Local-DNS/
• https://dockerlabs.collabnix.com/intermediate/networking/Configuring_DNS.html

Apart from that there is now a community container that can be added to the AIO stack: https://github.com/nextcloud/all-in-one/tree/main/community-containers/pi-hole

If you registered your domain via the built-in deSEC integration, the dnsmasq community container is automatically enabled and resolves your Nextcloud domain to the server's local IP for LAN clients. You only need to point your router's DHCP DNS server to the AIO host — see the dnsmasq documentation for details.

How to overwrite the local DNS resolution for some domains or add extra hosts to the containers?

For some use cases, you might need to overwrite the local DNS resolution of some domains inside the containers. On Linux, you can do so either by using a local DNS server as described in the section above and add a local DNS entry into the dns server and make your containers use that DNS server.

Another solution on Linux, depending on your network and docker configuration, it might also work to simply edit the /etc/hosts file. Add your custom entry like 172.18.0.1 mail.example.com as additional line to the file and restart docker which should automatically push the entry to all docker containers.

How to skip the domain validation?

If you are completely sure that you've configured everything correctly and are not able to pass the domain validation, you may skip the domain validation by adding --env SKIP_DOMAIN_VALIDATION=true to the docker run command of the mastercontainer (but before the last line ghcr.io/nextcloud-releases/all-in-one:latest! If it was started already, you will need to stop the mastercontainer, remove it (no data will be lost) and recreate it using the docker run command that you initially used).

Alternatively, if the container is already running, reload the AIO interface with the param skip_domain_validation to skip the domain validation on the fly: e.g. https://ip.address.of.the.server:8080/containers?skip_domain_validation.

How to resolve firewall problems with Fedora Linux, RHEL OS, CentOS, SUSE Linux and others?

It is known that Linux distros that use firewalld as their firewall daemon have problems with docker networks. In case the containers are not able to communicate with each other, you may change your firewalld to use the iptables backend by running:

sudo sed -i 's/FirewallBackend=nftables/FirewallBackend=iptables/g' /etc/firewalld/firewalld.conf
sudo systemctl restart firewalld docker

Afterwards it should work.

See https://dev.to/ozorest/fedora-32-how-to-solve-docker-internal-network-issue-22me for more details on this. This limitation is even mentioned on the official firewalld website: https://firewalld.org/#who-is-using-it

What can I do to fix the internal or reserved ip-address error?

If you get an error during the domain validation which states that your ip-address is an internal or reserved ip-address, you can fix this by first making sure that your domain indeed has the correct public ip-address that points to the server and then adding --add-host yourdomain.com: to the docker run command of the mastercontainer (but before the last line ghcr.io/nextcloud-releases/all-in-one:latest! If it was started already, you will need to stop the mastercontainer, remove it (no data will be lost) and recreate it using the docker run command that you initially used) which will allow the domain validation to work correctly. And so that you know: even if the A record of your domain should change over time, this is no problem since the mastercontainer will not make any attempt to access the chosen domain after the initial domain validation.

How to adjust the MTU size of the docker network

You can adjust the MTU size of the docker network by creating it beforehand with the custom MTU:

docker network create --driver bridge --opt com.docker.network.driver.mtu=1440 nextcloud-aio

When you open the AIO interface for the first time after you execute the docker run command, it will automatically connect to the nextcloud-aio network with the custom MTU. Keep in mind that if you previously started the mastercontainer without creating the network with the extra options, you will need to remove the old nextcloud-aio network and recreate it with the new configuration.

If you want to use docker compose, you can check out the comments in the compose.yaml file for more details.

Infrastructure

Which CPU architectures are supported?

You can check this on Linux by running: uname -m

• x86_64/x64/amd64
• aarch64/arm64/armv8

Disrecommended VPS providers

• Older Strato VPS using Virtuozzo caused problems though ones from Q3 2023 and later should work.

If your VPS has a /proc/user_beancounters file and a low numproc limit set in it
your server will likely misbehave once it reaches this limit
which is very quickly reached by AIO, see here.

• Hostingers VPS seem to miss a specific Kernel feature which is required for AIO to run correctly. See here.

Recommended VPS

In general recommended VPS are those that are KVM/non-virtualized as Docker should work best on them.

Note on storage options

• SD-cards are disrecommended for AIO since they cripple the performance and they are not meant for many write operations which is needed for the database and other parts
• SSD storage is recommended
• HDD storage should work as well but is of course much slower than SSD storage

Are there known problems when SELinux is enabled?

Yes. If SELinux is enabled, you might need to add the --security-opt label:disable option to the docker run command of the maste