Nextcloud AIO domain not working

Hello there,

I installed the Nextcloud AIO and Nginx Proxy Manager via docker. Both Webinterfaces are running fine and I’m currently at the containers page of Nextcloud, where you have to enter your domain in order to proceed.

I then tried to setup DDNS and wildcard subdomains for my domain on Namecheap, after that I configured Nginx Proxy Manager following this guide, but when I click on “Save” I get an internal Error message.

I’m kinda stuck now, I also uploaded Screenshots of my configurations to Imgur (couldn’t upload them here for some reason).
What am I doing wrong?

Thanks for your help!

Hi, can you post the mastercontainer logs here since you said that you get an internal server error?

Also, can you post the docker run commands or docker-compose files here that you used?

For Nginx Proxy Manager, I used docker compose and had to modify the ports a little to get it up running:

version: '3'
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '85:80'
      - '81:81'
      - '444:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

For Nextcloud I used this command:

# For x64 CPUs and without reverse proxy already in place:
sudo docker run \
--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 \
nextcloud/all-in-one:latest

Nextcloud mastercontainer log is here,

and the Nginx Proxy Manager log is here.

So basically you have used the wrong docker run command for AIO. Please read the reverse proxy docs again. There is a different docker run command described.

I tried it two times again.

First time, ich used the docker docker-compose command from this guide:

version: "3.8"

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer
services:
  nginx_proxy_manager:
    image: jc21/nginx-proxy-manager:latest
    restart: unless-stopped
    container_name: nginx-proxy-manager
    network_mode: host
    environment: # Uncomment this if IPv6 is not enabled on your host
      - DISABLE_IPV6=true # Uncomment this if IPv6 is not enabled on your host
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
  nextcloud:
    image: nextcloud/all-in-one:latest
    restart: unless-stopped
    container_name: nextcloud-aio-mastercontainer
    depends_on:
      - nginx_proxy_manager
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro
    ports:
      - 8080:8080
    environment:
      - APACHE_PORT=11000
     - NEXTCLOUD_TRUSTED_DOMAINS=nc.mydomain.premio 192.168.0.6
     - TRUSTED_PROXIES=192.168.0.6

Since I wasn’t really sure, how the last two lines should look like, I took them from this other guide.

On my second attempt, I used this command, that as described in the reverse proxy docs:

# For x64 CPUs:
sudo docker run \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 8080:8080 \
-e APACHE_PORT=11000 \
-e APACHE_IP_BINDING=0.0.0.0 \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
nextcloud/all-in-one:latest

Also here are the logs from my second attempt for the nextcloud mastercontainer and Nginx Proxy Manager.

Both times I got to the page, where Nextcloud asks for my domain.
Nginx Proxy Manager still shows an Internal Error message, so basically the problem I had in the beginning is still the same.

This looks good.

Can you also post a screenshot of your NPM config for the domain?

1 Like

I uploadet them to imgur, since I cant upload more than 2 pictures:

(I didn’t touch the “Custom locations” part)

Looks good. In that case you could skipp the domain validation: GitHub - nextcloud/all-in-one: Nextcloud AIO stands for Nextcloud All In One and provides easy deployment and maintenance with most features included in this one Nextcloud instance.

1 Like

Thank you very much for the help!

It’s still not working, but I now know why.
I’m using a Pyur router (Kabelbox), even though I forwarded all necessary ports (or so I thought), the Pyur router is not able to do so (just locally). I will try it again, once my new router arrives.

1 Like