Nextcloud-AIO on Docker doesn't listen to 11000

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, , ,
1

Trying to deploy Nextcloud-AIO on the latest TrueNAS Scale version, but I can’t pass the domain validation step.

If I try to reach http:/ /10.166.26.49:11000 unable to reach.

This is my docker-compose file:

networks:
  laforcenet:
    external: True
services:
  nextcloud-aio-mastercontainer:
    container_name: nextcloud-aio-mastercontainer
    environment:
      - APACHE_IP_BINDING=0.0.0.0
      - APACHE_PORT=11000
      - NEXTCLOUD_DATADIR=/mnt/Data/CiteDesNuages/Data
      - NEXTCLOUD_MOUNT=/mnt/Data/CiteDesNuages/Config
      - NEXTCLOUD_MEMORY_LIMIT=4096M
    image: ghcr.io/nextcloud-releases/all-in-one:latest
    init: True
    networks:
      laforcenet:
        ipv4_address: 10.166.26.49
    restart: 'no'
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro
volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer

I also tried to simply use https:/ /10.166.26.49:8080 with NPM instead of http:/ /10.166.26.49:11000 but curl https:/ /domain.com will always return ““ (note that curl https:/ /domain.com/setup return some html code)

2025-12-04 19:29:37.100634+00:00NOTICE: PHP message: The response of the connection attempt to "https://domain.com:443" was: 
2025-12-04 19:29:37.100731+00:00NOTICE: PHP message: Expected was: sdfsdfsdfds
2025-12-04 19:29:37.100775+00:00NOTICE: PHP message: The error message was: 
2025-12-04 19:29:37.100793+00:00NOTICE: PHP message: Please follow https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#how-to-debug in order to debug things!

Not sure how to debug that,

2

Hi, can you follow https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#7-how-to-debug-things?

1 Like
3 
7. Check if after the mastercontainer was started, the reverse proxy if running inside a container, can reach the provided apache port. You can test this by running nc -z localhost 11000; echo $? from inside the reverse proxy container. If the output is 0, everything works. Alternatively you can of course use instead of localhost the ip-address of the host here for the test.

return: 1

4

Can you post the output of sudo netstat -tupln here (please run it on the server that runs the docker daemon).

1 Like
5

oh! The port is exposed on the host, and not on the container IP I configured…

root@CoruscantZ[~]# sudo netstat -tupln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      0 0.0.0.0:11000           0.0.0.0:*               LISTEN      3749044/docker-prox

It works if I use the host IP, any way I can expose the port on the container instead?

6

The apache port is exposed on a different container named nextcloud-aio-apache. You can point to that. See all-in-one/reverse-proxy.md at main · nextcloud/all-in-one · GitHub and the On the same server in a Docker container section

1 Like