Error installing Nextcloud AiO docker on Synology

fietserse · December 10, 2025, 7:56pm

Support intro

Sorry to hear you’re facing problems.

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:

Official documentation (searchable and regularly updated)
How to topics and FAQs
Forum search

(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.

The Basics

Nextcloud Server version (e.g., 29.x.x):
- latest, on Dec 10, 2025
Operating system and version (e.g., Ubuntu 24.04):
- DSM 7.3.2-86009
Web server and version (e.g, Apache 2.4.25):
- replace me
Reverse proxy and version _(e.g. nginx 1.27.2)
- replace me
PHP version (e.g, 8.3):
- replace me
Is this the first time you’ve seen this error? (Yes / No):
- replace me
When did this problem seem to first start?
- During installation
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
- AIO on Docker, using Nextcloud installation guide
Are you using CloudfIare, mod_security, or similar? (Yes / No)
- replace me

Summary of the issue you are facing:

Hi there, I am trying to install AIO docker on a brand new Synology DS725+, using this guide: GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

I did connect to the NAS by SSH and used the text with proposed changes for Synology:
sudo docker run
–init
–sig-proxy=false
–name nextcloud-aio-mastercontainer
–restart always
–publish 80:80
–publish 8080:8080
–publish 8443:8443
–volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config
–volume /volume1/docker/docker.sock:/var/run/docker.sock:ro
–env WATCHTOWER_DOCKER_SOCKET_PATH=“/volume1/docker/docker.sock”
–env DOCKER_API_VERSION=1.44
–env APACHE_PORT=11000

ghcr . io/nextcloud-releases/all-in-one:latest

(Sorry, last line was also text in SSH, but if I paste the ghcr . io without spaces it creates an URL link…)

Also tried some varying, nothing worked…

Seems to be something with port 80? No idea what to do, should be nothing else running on it.
I do have an old Win 10 PC with Docker Desktop and Nextcloud AIO open to internet that I know use (which has port forwarding 80 and 443), but even when I closed down this forwarding I had the same issues with this new NAS.

Can someone tell me what goes wrong and how to handle this?

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

Install clean NAS, latest DSM
Install container manager
Enable SSH
Log in to SSH, use text as above

Log entries

SSH (CMD in Windows 11)

Unable to find image ‘``ghcr.io/nextcloud-releases/all-in-one:latest’`` locally
latest: Pulling from nextcloud-releases/all-in-one
2d35ebdb57d9: Pull complete
df5069f8c3d3: Pull complete
b1ecf0dc6565: Pull complete
fc3f8ac1a5c4: Pull complete
a285d7c9f090: Pull complete
73113f50c868: Pull complete
a50dd8c0a1b0: Pull complete
4ef6ed91e76e: Pull complete
cbc63626f647: Pull complete
70908ec0ebb1: Pull complete
4f4fb700ef54: Pull complete
ceafe65c3d0e: Pull complete
4936c8f622a5: Pull complete
8b78deb6b511: Pull complete
8b6373b507ae: Pull complete
36e75819cc46: Pull complete
9630ada56147: Pull complete
9f4aec1faf42: Pull complete
41f111939e1d: Pull complete
48d31364b03b: Pull complete
f3c1f8c3c05f: Pull complete
Digest: sha256:33f46abc48b1a12aa6eef5dda9cdf39403f4b5f8537b3791e8f45ffcd7928992
Status: Downloaded newer image for ``ghcr.io/nextcloud-releases/all-in-one:latest
docker: Error response from daemon: driver failed programming external connectivity on endpoint nextcloud-aio-mastercontainer (937f56bc882907e70995f48a3777a908c4c7929fb8940b905a4fca05276ab9fb): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use.

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.

jtr · December 10, 2025, 8:37pm

Does it start alright if you drop this part?

fietserse · December 11, 2025, 8:00pm

Hi jtr, thanx for responding!

No, it does not start alright, but the error is different. It now says:

Status: Downloaded newer image for ``ghcr.io/nextcloud-releases/all-in-one:latest
docker: Error response from daemon: Bind mount failed: ‘/volume1/docker/docker.sock’ does not exist.

jtr · December 11, 2025, 8:22pm

Does it exist on your Synology/host? As the docs say, it may not be in that location.

fietserse · December 11, 2025, 8:28pm

I do have a folder “docker” on “volume1”, is that enough? Should there be a file “docker.sock” in it? In the File Station I do not have any other folder.

jtr · December 11, 2025, 8:43pm

Please see the note in the Synology section. It has alternative paths.

Yes, the socket file must exist; but you must not create it manually. It’s provided by your Docker installation.

fietserse · December 12, 2025, 8:17am

Okay, so I used the ‘standard’ text, var/run/docker.sock.

I get:

Status: Downloaded newer image for ``ghcr.io/nextcloud-releases/all-in-one:latest
Trying to fix docker.sock permissions internally…
Adding internal www-data to group root
Error response from daemon: client version 1.44 is too new. Maximum supported API version is 1.43
ERROR: Error response from daemon: client version 1.44 is too new. Maximum supported API version is 1.43
errors pretty printing info
ERROR: Error response from daemon: client version 1.44 is too new. Maximum supported API version is 1.43
errors pretty printing info
Error response from daemon: client version 1.44 is too new. Maximum supported API version is 1.43
It seems like you did not give the mastercontainer the correct name? (The ‘nextcloud-aio-mastercontainer’ container was not found.)
Using a different name is not supported since mastercontainer updates will not work in that case!
If you are on docker swarm and try to run AIO, see ``https://github.com/nextcloud/all-in-one#can-i-run-this-with-docker-swarm

I also tried with the suggested –env DOCKER_API_VERSION=1.44 \

That doesn’t make it better, I now get:

Status: Downloaded newer image for ``ghcr.io/nextcloud-releases/all-in-one:latest
Trying to fix docker.sock permissions internally…
Adding internal www-data to group root
DOCKER_API_VERSION was found to be set to ‘1.44’.
Please note that only v1.44 is officially supported and tested by the maintainers of Nextcloud AIO.
So you run on your own risk and things might break without warning.
Error response from daemon: client version 1.44 is too new. Maximum supported API version is 1.43
ERROR: Error response from daemon: client version 1.44 is too new. Maximum supported API version is 1.43
errors pretty printing info
ERROR: Error response from daemon: client version 1.44 is too new. Maximum supported API version is 1.43
errors pretty printing info
Error response from daemon: client version 1.44 is too new. Maximum supported API version is 1.43
It seems like you did not give the mastercontainer the correct name? (The ‘nextcloud-aio-mastercontainer’ container was not found.)
Using a different name is not supported since mastercontainer updates will not work in that case!
If you are on docker swarm and try to run AIO, see ``https://github.com/nextcloud/all-in-one#can-i-run-this-with-docker-swarm

szaimen · December 12, 2025, 8:19am

Hi, based on that you need to use
--env DOCKER_API_VERSION=1.43

fietserse · December 12, 2025, 8:38am

Okay, that’s better, but still not finished

I now get:

Status: Downloaded newer image for ghcr.io/nextcloud-releases/all-in-one:latest
Trying to fix docker.sock permissions internally…
Adding internal www-data to group root
DOCKER_API_VERSION was found to be set to ‘1.43’.
Please note that only v1.44 is officially supported and tested by the maintainers of Nextcloud AIO.
So you run on your own risk and things might break without warning.
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
..+…+…+…+..+.+…+…+++++++++++++++++++++++++++++++++++++++++++++.+…+…+…+…+…+..+…+…+…+…+++++++++++++++++++++++++++++++++++++++++++++…+…+…+…+…+…+…+…+…+…+…+…+…+..+.+…+…+…+.+++++
…+..+.+…+…+..+…+.+++++++++++++++++++++++++++++++++++++++++++++..+…+++++++++++++++++++++++++++++++++++++++++++++…+…+…+…+…+…+..+…+…+…+…+…+…+…+…+…+…+…+…+.+…+..+…+…+…+…+.+…+…+…+…+…+…+.+…+…+..+…+…+…+..+…+..+…+…+…+…+…+…+…+.+…+..+.+…+…+…+…+…+…+…+…+..+…+…+…+…+…+..+…+…+..+…+…+…+…+++++

Initial startup of Nextcloud All-in-One complete!
You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
E.g. https://internal.ip.of.this.server:8080
⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!

If your server has port 80 and 8443 open and you point a domain to your server, you can get a valid certificate automatically by opening the Nextcloud AIO Interface via:

/usr/lib/python3.12/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html. The pkg_resources package is slated for removal as early as 2025-11-30. Refrain from using this package or pin to Setuptools<81.
import pkg_resources
{“level”:“warn”,“ts”:1765527665.3340032,“msg”:“failed to set GOMAXPROCS”,“error”:“open /sys/fs/cgroup/cpu/cpu.cfs_quota_us: no such file or directory”}
{“level”:“info”,“ts”:1765527665.3342633,“msg”:“GOMEMLIMIT is updated”,“package”:“github.com/KimMachineGun/automemlimit/memlimit",“GOMEMLIMIT”:15048843264,"previous”:9223372036854775807}
{“level”:“info”,“ts”:1765527665.334292,“msg”:“using config from file”,“file”:“/Caddyfile”}
{“level”:“info”,“ts”:1765527665.3358514,“msg”:“adapted config to JSON”,“adapter”:“caddyfile”}
{“level”:“info”,“ts”:1765527665.3391955,“msg”:“serving initial configuration”}
[12-Dec-2025 08:21:05] NOTICE: fpm is running, pid 148
[12-Dec-2025 08:21:05] NOTICE: ready to handle connections
[Fri Dec 12 08:21:05.409528 2025] [mpm_event:notice] [pid 143:tid 143] AH00489: Apache/2.4.66 (Unix) OpenSSL/3.5.4 configured – resuming normal operations
[Fri Dec 12 08:21:05.409566 2025] [core:notice] [pid 143:tid 143] AH00094: Command line: ‘httpd -D FOREGROUND’

Seems like a good result, but I still can’t open the page on <my.nas.ip.address>:8080, it says:

Bad Request

Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

Apache/2.4.66 (Unix) Server at localhost Port 8080

and if I try port 8443 (with https), it says:

Secure Connection Failed

An error occurred during a connection to 192.168.178.71:8443. Peer reports it experienced an internal error.

Error code: SSL_ERROR_INTERNAL_ERROR_ALERT

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.

Please contact the website owners to inform them of this problem.

szaimen · December 12, 2025, 9:04am

You need to use https://<my.nas.ip.address>:8080

fietserse · December 12, 2025, 9:07am

I thought I did, but apparently not Thanx!

matkinson · December 17, 2025, 4:34pm

Take a look at this alernative How To from Marius. Well written like most of his articles and has helped me with many of my Synology maddening quirks. I’ve also sent him some support in the past as he’s saved me a ton of time on a few occasions. Cheers