nextcloud AIO and traefik 3 setup help needed

ℹ️ Support
, , , ,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):

    • 12.3.0AIO

  • Operating system and version (e.g., Ubuntu 24.04):

    • ubuntu 24.04

  • Reverse proxy and version _(e.g. nginx 1.27.2)

    • traefik 3

  • Is this the first time you’ve seen this error? (Yes / No):

    • yes

    When did this problem seem to first start?

    • right from install

  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)

    • AIO

  • Are you using CloudfIare, mod_security, or similar? (Yes / No)

    • no

Summary of the issue you are facing:

This is a brand new install, I have the installation completed but I cannot get it to display any pages except the port 8080 management site. I get a “404 page not found” error on both port 11000 locally and port 80/443 using the domain name.

I have read the reverse proxy documentation, and honestly, the document leaves a considerable amount of required detail out, it assumes that the reader is an expert with traefik and provides little in the way of explanation on how to actually configure it. I have several other docker containers running on this server and all of those are working properly.

I created the nextcloud.yml file by copying and pasting the example.


http:
  routers:
    nextcloud:
      rule: "Host(`data.mydomain.org`)"
      entrypoints:
        - "https"
      service: nextcloud
      middlewares:
        - nextcloud-chain
      tls:
        certresolver: "letsencrypt"

  services:
    nextcloud:
      loadBalancer:
        servers:
          - url: "http://0.0.0.0:11000" # Adjust to match APACHE_PORT and APACHE_IP_BINDING. See https://github.com/nex>

  middlewares:
    nextcloud-secure-headers:
      headers:
        hostsProxyHeaders:
          - "X-Forwarded-Host"
        referrerPolicy: "same-origin"

    https-redirect:
      redirectscheme:
        scheme: https

    nextcloud-chain:
      chain:
        middlewares:
          # - ... (e.g. rate limiting middleware)
          - https-redirect
          - nextcloud-secure-headers

From my compose.yaml:

services:
  nextcloud-aio-mastercontainer:
    image: ghcr.io/nextcloud-releases/all-in-one:latest # This is the container image used. You can switch to ghcr.io/n>
    init: true # This setting makes sure that signals from main process inside the container are correctly forwarded to>
    restart: always # This makes sure that the container starts always together with the host OS. See https://docs.dock>
    container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not wo>
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the >
      - /var/run/docker.sock:/var/run/docker.sock:ro # May be changed on macOS, Windows or docker rootless. See the app>
#    network_mode: bridge # This adds the container to the same network as docker run would do. Comment this line and u>
    networks:
      - web
    ports:
      - "8081:8080"
    environment:
      - APACHE_PORT=11000
      - APACHE_IP_BINDING=0.0.0.0
      - SKIP_DOMAIN_VALIDATION=true
      - APACHE_ADDITIONAL_NETWORK=web

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer

I am fairly certain that the http > https > port 11000 redirect is where the problem lies, I just cannot figure out what I am missing.

2

Based on the rest of your config, this should probably be http://nextcloud-aio-apache:11000.

Remove this from your Compose file.

Via what target IP? And what do you mean by “locally”? Based on your posted Docker config, it’s unlikely to be reachable other than from within your reverse proxy container.

3 Likes
3

- url: “http://10.0.0.3:11000”

That was the solution. I needed to set it to the private ip of the host server.

2 Likes