NextCloud AIO when behind NPM?

Apps and Virtualization
1

Using the guide I found here, I am able to get AIO started and log into the set up screen.
My problems start when I try to submit the domain. I’m guessing it has something to do with the fact that Nginx Proxy Manager is already consuming ports 80 and 443 on the host I installed AIO on.
Or maybe not, I’m still pretty new to all this. The AIO GUI gives me this:

Domain does not point to this server or the reverse proxy is not configured correctly. See the mastercontainer logs for more details. ('sudo docker logs -f nextcloud-aio-mastercontainer')

And in Dockge I get this:

NOTICE: PHP message: Info: It seems like the ip-address of ncaio.technospider.com is set to an internal or reserved ip-address. (It was found to be set to '192.168.2.2')
NOTICE: PHP message: The response of the connection attempt to "https://ncaio.technospider.com:44</html>nter>openresty</center>1></center>d>
NOTICE: PHP message: Expected was: d46776264d5af51105edccdf6ee7c35b8b8b7413b20b83d3
NOTICE: PHP message: The error message was: 
NOTICE: PHP message: Please follow https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#6-how-to-debug-things in order to debug things!

Any help overcoming these issues would be greatly appreciated.

2

I was able to get past this issue by using:

SKIP_DOMAIN_VALIDATION=true

as an environment variable in the compose file.
Since I was sure my domain was set up correctly and NPM was pointing to the right spot, I pressed on.

Looks like everything I’ve tested so far is up and running correctly now.
I have not had a chance to try the Talk features yet but there are no errors in the admin section so I’m hopeful.

3

No, the AOI stack starts a different container that uses port 11000 by default there is where you should point you NPM.

See this md for more info on how to configure npm with nc-AIO

all-in-one/reverse-proxy.md at main · nextcloud/all-in-one · GitHub

you also need to set your env variables correct

For example APACHE_PORT: 11000 and APACHE_IP_BINDING: 127.0.0.1

4

I’m fairly certain that I already had NPM pointed to 11000 and was still getting that issue. But it was closing in on 2300 hours and I might be conflating 2 different issues I was working on.
Either way, it immediately worked as soon as I skipped the verification.

This was my compose file:

services:
  nextcloud:
    image: nextcloud/all-in-one:latest # Must be changed to 'nextcloud/all-in-one:latest-arm64' when used with an arm64 CPU
    restart: always
    container_name: nextcloud-aio-mastercontainer
    volumes:
      - /mnt/LCARS/applications/nextcloud-aio/nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro
    ports:
      - 8080:8080
    environment:
      - APACHE_PORT=11000
      - NEXTCLOUD_DATADIR=/mnt/LCARS/applications/nextcloud_aio/data # Allows to set the host directory for Nextcloud's datadir. See https://github.com/nextcloud/all-in-one#how-to-change-the-default-location-of-nextclouds-datadir
      - NEXTCLOUD_MOUNT=/mnt/tank/docker/nextcloud_aio # Allows the Nextcloud container to access the chosen directory on the host. See https://github.com/nextcloud/all-in-one#how-to-allow-the-nextcloud-container-to-access-directories-on-the-host
      - NEXTCLOUD_MEMORY_LIMIT=4096M
      - SKIP_DOMAIN_VALIDATION=true
networks: {}
volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer

Actually, odd.
What should the NEXTCLOUD_MOUNT point to? That’s the default entry and I didn’t change it. What impact does that have and where should I actually point it?

5

It’s just there for adding local “external storage”.

I have removed that ENV variable and the container works perfectly fine. It can only access it’s mounted data directory, but that’s the behavior I expect so no issues there.