I am installing the nextcloud-aio docker container and can never seem to get it to access 11000. No other application is using port 11000. I’m able to access 8080 and go through the setup process however I can’t get pass that after all of the containers are up and running. I get a 502 bad gateway error. I’m a bit new to self hosting applications. I assumed that this would be the best way to host Nextcloud but maybe I’m wrong? I am using npm however I can’t even access Nextcloud through port 11000 locally when at home connected to the same network. This is my docker-compose file that I am using. I took it from the nextcloud-aio github page and just removed and changed what I thought was correct. I’m having a hard time finding a solution on reddit or anywhere online thus far.

Thank you.

services:
  nextcloud-aio-mastercontainer:
    image: nextcloud/all-in-one:latest
    init: true
    restart: unless-stopped
    container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not work correctly
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the built-in backup solution will not work
      - /var/run/docker.sock:/var/run/docker.sock:ro # May be changed on macOS, Windows or docker rootless. See the applicable documentation. If adjusting, don't forget to also set 'WATCHTOWER_DOCKER_SOCKET_PATH'!
    ports:
      # - 1080:80 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
      - 8080:8080
      # - 8443:8443 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
    environment: # Is needed when using any of the options below
      - APACHE_PORT=11000 # Is needed when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
      - APACHE_IP_BINDING=127.0.0.1 # Should be set when running behind a web server or reverse proxy (like Apache, Nginx, Cloudflare Tunnel and else) that is running on the same host. See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
      # - TALK_PORT=3478 # This allows to adjust the port that the talk container is using. See https://github.com/nextcloud/all-in-one#how-to-adjust-the-talk-port

volumes: # If you want to store the data on a different drive, see https://github.com/nextcloud/all-in-one#how-to-store-the-filesinstallation-on-a-separate-drive
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer # This line is not allowed to be changed as otherwise the built-in backup solution will not work

  • thekrautboyB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    8080 in the case of NC AiO is for not for Nextcloud but for the AiO Container via https.

    The Apache port is not internal, but accessible via IP:11000. But it is exclusively for use via reverse proxy.

    NC AiO dies things differently than pure NC.

    I know NC AiO is a bit weird and unique. But i can only go by what OP is sharing as the compose they are attempting. And none of that makes sense as i said.

    to be blunt, and maybe a bit of a jerk, but i think OP did not read the documentation that is linked right in the compose file or the github page. NC AiO has excellent documentation of how to set it up. Thats it, i said it :/

    A lot of people are allergic to properly reading documentation and instead they come to places like here and ask others to fix their mistakes.