Help with Nextcloud AIO installation on TerraMaster F4-425 plus (Docker + Nginx Proxy Manager) [SOLVED]

[Din0]

Hi everyone,

I am a new owner of the TerraMaster F4-425 Plus TOS ver. 6.0.794-01324. Could someone help me with installing Nextcloud AIO?

I am currently running Nextcloud on a QNAP TS-253 using a native Apache web server, so the configuration is completely different from the Docker setup I'm trying to build now.

Could someone please advise me on how to set this up, including the Docker Compose code and the correct port forwarding on the router? I’ve been struggling with this for 2 days with no luck. After installation, I cannot access Nextcloud via Nginx Proxy Manager.

Thanks, Aleš

[CursaYang]

Perhaps you can refer to the instructions in the official documentation for setup:
https://apps.nextcloud.com/apps/nextcloud_all_in_one
Our app store also provides simple Nextcloud applications.

[Din0]

Hi,

Thank you for the link, but referring me to the generic documentation does not solve the issue. I have already successfully installed the Docker container.

The problem is specific to TerraMaster TOS 6 network restrictions. Nextcloud AIO (and the Nginx Proxy Manager) requires ports 80 and 443 to be exposed for external access and SSL validation.

However, TOS 6 reserves ports 80 and 443 for the system interface (or internal Nginx), preventing Docker containers from using them.

My question is specific:

Is there an official way in TOS 6 to release ports 80 and 443 so they can be used effectively by Docker containers?

Or does TOS 6 fully support Docker Macvlan networks so I can assign a separate IP address to the container and bypass the NAS port conflict entirely?

Please advise on how to bypass this system limitation.

Thanks, Aleš

[Gremlin]

Is there an official way in TOS 6 to release ports 80 and 443 so they can be used effectively by Docker containers?

Yes. Tos Control Panel > Network >General

Last segment* allows re-direction and specifically mentions those ports.
You just have to accept the contraints of having to nominate specific ports for accessing if you go "off-piste".
*{May vary depending on the TOS release, but it has been there for a long time.}
**{Like the man said, RTFM}

[Din0]

Hi Gremlin,

Thank you for the specific tip regarding the Network settings. I will double-check the manual as you suggested.

Coming from a QNAP environment (where I used a native Apache setup for years), the configuration logic in TOS 6 and Docker is quite different for me. That is why I was asking if someone could share a comprehensive workflow or a proven setup guide. I wasn't just looking for one setting, but rather trying to understand the correct way to link NPM and Nextcloud AIO on this specific platform without breaking anything.

I appreciate your help.

Best regards, Aleš

[Din0]

Hi everyone,

Just a quick update – I managed to get it working!

I am now successfully running Nextcloud AIO in Docker behind Nginx Proxy Manager (NPM). I was able to configure NPM to listen on standard ports 80 and 443, which handles the SSL termination and forwards traffic to the Nextcloud container correctly.

Everything is running smoothly now. Thanks for the help!

Aleš

[sanira]

Great to hear you got Nextcloud AIO working with NPM! It can be tricky adjusting to TOS and Docker, so props for sticking with it. If you ever decide to share a quick guide on your steps, it could really help others who are struggling too

[Din0]

Hi everyone,

Since some of you asked for a working solution, here is my complete setup for running Nextcloud AIO behind Nginx Proxy Manager (NPM) on TOS 6.
Step 1: Release System Ports (Crucial!)

Before deploying the container, you must ensure ports 80 and 443 are free. By default, TOS reserves them.

Go to Control Panel > Network > General.

Uncheck/Disable "Force redirect HTTP to HTTPS" (or look for "Release ports 80/443").

Apply settings. Note: After this, you will need to access your NAS UI via the specific port (e.g., http://NAS-IP:8181).

Code: Select all

version: '3.8'

networks:
  proxy-network:
    name: proxy-network
    driver: bridge

services:
  
  nginx-proxy-manager:
    image: 'jc21/nginx-proxy-manager:latest'
    container_name: nginx-proxy-manager
    restart: unless-stopped
    networks:
      - proxy-network
    ports:
      - '80:80'      # HTTP entry
      - '443:443'    # HTTPS entry
      - '81:81'      # NPM Admin UI
    volumes:
      - /Volume1/docker/npm/data:/data
      - /Volume1/docker/npm/letsencrypt:/etc/letsencrypt

  nextcloud-aio-mastercontainer:
    image: nextcloud/all-in-one:latest
    container_name: nextcloud-aio-mastercontainer
    init: true
    restart: always
    networks:
      - proxy-network
    ports:
      - "8080:8080"  # AIO Admin Interface
    environment:
      - APACHE_PORT=11000       # Key setting for Reverse Proxy
      - APACHE_IP_BINDING=0.0.0.0
    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

Step 3: NPM Configuration

Once containers are running:

Log into Nginx Proxy Manager (http://NAS-IP:81).

Add a new Proxy Host.

Domain Name: your.domain.com

Scheme: http

Forward Hostname / IP: nextcloud-aio-mastercontainer (since they share the same network) OR your NAS IP.

Forward Port: 11000 (This matches the APACHE_PORT variable in the yaml).

Enable Websockets Support and Block Common Exploits.

In the SSL tab, request a new Let's Encrypt certificate and enable "Force SSL".

Now you can finish the Nextcloud setup at https://NAS-IP:8080 by entering your domain.

Hope this helps! Aleš

Edit:
I have noticed that currently, I am only able to connect external folders via SMB/CIFS.
Does anyone know the correct procedure to connect storage as "Local" in this AIO Docker setup?
I would prefer to map a local folder from the NAS directly (e.g., /Volume1/Public) to avoid the SMB overhead, but I am not sure how to pass this path through the AIO container correctly so that Nextcloud can see it.
If you have a working method or configuration for this, please share it.
Thanks!