Nextcloud AIO container stuck "starting" with Nginx Proxy Manager (NPM)(non standard port)

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

Hello everyone,I’m encountering an issue deploying Nextcloud AIO via Portainer with Nginx Proxy Manager (NPM). My nextcloud-aio-nextcloud container gets stuck in a “starting” state, and I suspect it’s a networking or domain configuration problem.My Setup:

  • Nextcloud AIO: Deployed via docker-compose.yaml in Portainer.
  • Reverse Proxy: Nginx Proxy Manager.
  • Domain Access: Externally, I access Nextcloud via https://cloud.example.com:8443.
  • Port Forwarding: My ISP forwards public port 8443 to 443 on my server’s internal IP. So, NPM receives traffic on port 443.
  • DNS: Cloudflare is my DNS provider, configured in “DNS only” mode (grey cloud), so no Cloudflare proxying occurs.
  • SSL: Let’s Encrypt certificates for cloud.example.com are successfully obtained by NPM using a Cloudflare API token.

Current docker-compose.yaml for Nextcloud AIO:

services:
  nextcloud-aio-mastercontainer:
    image: ghcr.io/nextcloud-releases/all-in-one:latest
    init: true
    restart: always
    container_name: nextcloud-aio-mastercontainer
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro
    network_mode: bridge # Uses Docker's default bridge network
    ports:
      # - 80:80 # Commented out as NPM handles this
      - 8080:8080 # For AIO admin interface access
      # - 8443:8443 # Commented out as NPM handles this
    environment:
      APACHE_PORT: 11000
      APACHE_IP_BINDING: 127.0.0.1 # Apache binds only to localhost within its container
      NEXTCLOUD_DATADIR: /volume1/docker/nextcloud/data
      SKIP_DOMAIN_VALIDATION: true

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer

Nginx Proxy Manager Configuration (Details tab):

  • Domain Names: cloud.example.com
  • Scheme: http
  • Forward Hostname / IP: localhost
  • Forward Port: 11000
  • Websockets Support: Enabled.

When I initialize AIO via https://<server_ip>:8080, I enter cloud.example.com as the domain. I also attempted to use cloud.example.com:8443, but the domain input field in the AIO setup does not allow including port numbers.It seems the nextcloud-aio-nextcloud container cannot properly start or connect, likely because the APACHE_IP_BINDING is set to 127.0.0.1 (preventing NPM from reaching it) and potential networking isolation between AIO’s containers and NPM.What am I doing wrong in this setup, and what specific changes are needed in my docker-compose.yaml and/or NPM configuration to make Nextcloud AIO start correctly?

Thank you for your help!

2

Hey @przemoerb welcome to the Community :waving_hand:

this may be what you’re looking for:

3

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.