Unable to use Synology DSM's Reverse Proxy on Nextcloud AIO

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):
    • Nextcloud AIO v12.5.0
  • Operating system and version (e.g., Ubuntu 24.04):
    • DSM
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • Synology DSM Reverse Proxy
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • At installation
  • 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:

Hi everyone,
I’m trying to install Nextcloud AIO on my Synology NAS.
I use portainer to do so.

I have used the following yaml:

name: 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
    ports:
      - 8081:8080
    environment:
      APACHE_PORT: "11000"
      APACHE_IP_BINDING: "127.0.0.1"
      DOCKER_API_VERSION: "1.43"
      NEXTCLOUD_DATADIR: "/volume1/docker/nextcloud-aio/data"
      NEXTCLOUD_MOUNT: "/volume1/"
      WATCHTOWER_DOCKER_SOCKET_PATH: "/var/run/docker.sock"
      SKIP_DOMAIN_VALIDATION: "true"

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer

I also have activated a reverse proxy with the following settings:

Source
Hostname: nextcloud.myname.synology.me
Port: 443
HSTS disabled
Destination
Protocol: HTTPS
Hostname: 127.0.0.1
Port: 11000

The container launches, I access the first page properly.
It then asks for the following:
”Please type in the domain that will be used for Nextcloud and submit it.”
The problem is when I try to use nextcloud.myname.synology.me, i get the error “Domain does not point to this server or the reverse proxy is not configured correctly. See the mastercontainer logs for more details. (‘sudo docker logs -f nextcloud-aio-mastercontainer’)”

The log points to https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md#how-to-debug

However I’m not tech savvy enough to understand it.

Steps to replicate it (hint: details matter!):

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

PASTE HERE

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

PASTE HERE

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.