Docker AIO setup help

whatisausername · February 26, 2026, 3:16pm

I am new to NextCloud and installed it with the docker in linux with the instructions on the github page

https://github.com/nextcloud/all-in-one#nextcloud-all-in-one

my server has pi hole which uses port 443, which causes a kind of conflict with nextcloud. I don’t know how to get around this as the solutions are unclear/confusing to me. I don’t know what reverse proxies are or which specific things I need to install or any dependencies.

when I disable pi hole, the supposed first set up page will then show a field to submit a domain which is also another thing I struggled with. I have used duckdns to get a domain name and changed router settings to port forward my public ip to the private ip of my server but that did not work, I do not know what I am doing wrong.

Is there any way for me to bypass the domain requirement at all? What if I only want to use tailscale with it locally

So 2 things:

how can i set up nextcloud with pi hole active at the same time?

what exactly do I need to do to get around the domain submission?

scubamuc · February 26, 2026, 3:22pm

Hey @whatisausername welcome to the nextcloud community forum

why? do you access pihole externally? is that a docker install?

you could disable - "443:443/tcp" since you’re not accessing it externally and using tailscale anyhow… no need for https for local pihole and/or forward - "81:80/tcp", see here: GitHub - pi-hole/docker-pi-hole: The official Pi-hole Docker image from pi-hole.net

# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    ports:
      # DNS Ports
      - "53:53/tcp"
      - "53:53/udp"
      # Default HTTP Port
      - "80:80/tcp"
      # Default HTTPs Port. FTL will generate a self-signed certificate
      - "443:443/tcp"
      # Uncomment the line below if you are using Pi-hole as your DHCP server
      #- "67:67/udp"
      # Uncomment the line below if you are using Pi-hole as your NTP server
      #- "123:123/udp"

change the port mappings of pihole, see Fix Pihole web interface after installing Nextcloud AIO - Community Help - Pi-hole Userspace

also see this discussion: nextcloud-aio-pihole not reachable by aio containers, nextcloud.com check fails · nextcloud/all-in-one · Discussion #5384 · GitHub

this has been requested repeatedly, please use forum search:

github.com/nextcloud/all-in-one

local-instance.md

main

# Local instance
It is possible due to several reasons that you do not want or cannot open Nextcloud to the public internet. Perhaps you were hoping to access AIO directly from an `ip.add.r.ess` (unsupported) or without a valid domain.  However, AIO requires a valid certificate to work correctly. Below is discussed how you can achieve both: Having a valid certificate for Nextcloud and only using it locally.

### Content
- [1. Tailscale](#1-tailscale)
- [2. The normal way](#2-the-normal-way)
- [3. Use the ACME DNS-challenge](#3-use-the-acme-dns-challenge)
- [4. Use Cloudflare](#4-use-cloudflare)
- [5. Buy a certificate and use that](#5-buy-a-certificate-and-use-that)

## 1. Tailscale
This is the recommended way. For a reverse proxy example guide for Tailscale, see this guide by [@Perseus333](https://github.com/Perseus333): https://github.com/nextcloud/all-in-one/discussions/6817

## 2. The normal way
The normal way is the following:
1. Set up your domain correctly to point to your home network
1. Set up a reverse proxy by following the [reverse proxy documentation](./reverse-proxy.md) but only open port 80 (which is needed for the ACME challenge to work - however no real traffic will use this port).
1. Set up a local DNS-server like a pi-hole and configure it to be your local DNS-server for the whole network. Then in the Pi-hole interface, add a custom DNS-record for your domain and overwrite the A-record (and possibly the AAAA-record, too) to point to the private ip-address of your reverse proxy (see https://github.com/nextcloud/all-in-one#how-can-i-access-nextcloud-locally)
1. Enter the ip-address of your local dns-server in the daemon.json file for docker so that you are sure that all docker containers use the correct local dns-server.
1. Now, entering the domain in the AIO-interface should work as expected and should allow you to continue with the setup

This file has been truncated. show original

whatisausername · February 26, 2026, 8:48pm

why? do you access pihole externally? is that a docker install?

I don’t think no, I installed pihole without any complex docker setup (GitHub - pi-hole/pi-hole: A black hole for Internet advertisements). Whatever the case it’s conflicting with nextcloud’s setup so I must disable pi hole for it to show this page

I also do not know what you mean by “accessing it externally”.

When setting up nextcloud there is this long copy paste code with a part like publish XX:XX right? Do you mean that one of the numbers beside publish is accessed externally?

using this copy pate does not work because I end up with

“docker: Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint nextcloud-aio-mastercontainer (1df6f62ab0c63328e205a768cedbb0222e7b1f3396ac1b1fd6868392115c1462): failed to bind host port 0.0.0.0:80/tcp: address already in use”

So I think from this port 80 or 8080 was also used by pihole already so chatgpt suggested me to change to other port numbers for example (9080, 9443, 9081) by changing like this “publish 9080:8080”. pretend that 9080 is the port used for the first set up page, while the other 2 is for just unaccessible until i finish the set up with a valid domain.

I forgot to mentionthis too: I am trying to install this through ssh in the Windows Terminal so for that tailscale method you showed, are there anything I should be doing differently?

Should I put the server’s IP address instead of 127.0.0.1? what is an “apache”, is it something I have to install separately?