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)
The Basics
- Nextcloud Server version (e.g., 29.x.x):
Not sure, whatever the latest AIO version is as of 12/20/2025
- Operating system and version (e.g., Ubuntu 24.04):
LMDE 7 Gigi
- Web server and version (e.g, Apache 2.4.25):
Apache 2.4.65
- Reverse proxy and version _(e.g. nginx 1.27.2)
Nginx 2.13.5
- PHP version (e.g, 8.3):
Not installed
- Is this the first time you’ve seen this error? (Yes / No):
Yes
- When did this problem seem to first start?
Right after creating the docker container
- 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:
Today I was attempting to spin up the AIO for the first time after creating the initial docker container, and I found myself not being able to connect to the initial interface. At first it was because I mapped it to a port that was already being used, so I changed it, but after bringing up the container again my connection kept getting reset. When I looked at the container console with Dockge, the connection was being reset because the AIO was “disallowing” all connection attempts made to it. I tried to connect via localhost, 0.0.0.0, 127.0.0.1, and my machines local IP but none of them worked. After deleting and recreating the container a couple of times, it just stopped showing disallowed errors in the console.
I expected to run into a few issues during the setup process, but I wasn’t expecting to have trouble with just connecting to the initial interface. Any help would be appreciated, I’m very new to Nextcloud.
Steps to replicate it (hint: details matter!):
-
Create compose.yaml file within nextcloud folder
-
“sudo docker compose up -d”
-
Container is created, all goes well until it gets an error saying port 8081 is mapped to something else already (I have another service that uses it, unbeknownst to me at the time)
-
Change the port in the compose file, bring the container down and back up again, and I still can’t connect. I check console in Dockge and it says the service is disallowing all connections made to it.
-
I try deleting the container and remaking it a few times to no avail. Eventually it stops showing disallowed errors in the console and I still can’t connect.
Log entries
Nextcloud container log
nextcloud-aio-mastercontainer | Trying to fix docker.sock permissions internally...
nextcloud-aio-mastercontainer | Creating docker group internally with id 120
nextcloud-aio-mastercontainer | Initial startup of Nextcloud All-in-One complete!
nextcloud-aio-mastercontainer | You should be able to open the Nextcloud AIO Interface now on port 8080 of this server!
nextcloud-aio-mastercontainer | E.g. https://internal.ip.of.this.server:8080
nextcloud-aio-mastercontainer | ⚠️ Important: do always use an ip-address if you access this port and not a domain as HSTS might block access to it later!
nextcloud-aio-mastercontainer |
nextcloud-aio-mastercontainer | 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:
nextcloud-aio-mastercontainer | https://your-domain-that-points-to-this-server.tld:8443
nextcloud-aio-mastercontainer | /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.
nextcloud-aio-mastercontainer | import pkg_resources
nextcloud-aio-mastercontainer | [Sat Dec 20 06:34:04.019426 2025] [mpm_event:notice] [pid 167:tid 167] AH00489: Apache/2.4.66 (Unix) OpenSSL/3.5.4 configured -- resuming normal operations
nextcloud-aio-mastercontainer | [Sat Dec 20 06:34:04.019501 2025] [core:notice] [pid 167:tid 167] AH00094: Command line: 'httpd -D FOREGROUND'
nextcloud-aio-mastercontainer | [20-Dec-2025 06:34:04] NOTICE: fpm is running, pid 173
nextcloud-aio-mastercontainer | [20-Dec-2025 06:34:04] NOTICE: ready to handle connections
nextcloud-aio-mastercontainer | {"level":"info","ts":1766212444.043479,"msg":"maxprocs: Leaving GOMAXPROCS=8: CPU quota undefined"}
nextcloud-aio-mastercontainer | {"level":"info","ts":1766212444.0437195,"msg":"GOMEMLIMIT is updated","package":"github.com/KimMachineGun/automemlimit/memlimit","GOMEMLIMIT":30027445862,"previous":9223372036854775807}
nextcloud-aio-mastercontainer | {"level":"info","ts":1766212444.0437994,"msg":"using config from file","file":"/Caddyfile"}
nextcloud-aio-mastercontainer | {"level":"info","ts":1766212444.0462475,"msg":"adapted config to JSON","adapter":"caddyfile"}
nextcloud-aio-mastercontainer | {"level":"info","ts":1766212444.052203,"msg":"serving initial configuration"}
Compose file Configuration
services:
nextcloud-aio-mastercontainer:
image: ghcr.io/nextcloud-releases/all-in-one:latest
init: true
restart: always
container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed.
network_mode: bridge
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed.
- /var/run/docker.sock:/var/run/docker.sock:ro
ports:
- 8090:8090
environment:
APACHE_PORT: 11000 # Use this port in Nginx
# NC_TRUSTED_PROXIES: 172.18.0.3 # this is the NPM proxy ip address in the docker network !
FULLTEXTSEARCH_JAVA_OPTIONS: "-Xms1024M -Xmx1024M"
NEXTCLOUD_DATADIR: /nextcloud/ncdata # ⚠️ Warning: do not set or adjust this value after the initial Nextcloud installation is done!
NEXTCLOUD_MOUNT: /media/fabr412/ # Allows the Nextcloud container to access the chosen directory on the host.
NEXTCLOUD_UPLOAD_LIMIT: 1028G
NEXTCLOUD_MAX_TIME: 7200
NEXTCLOUD_MEMORY_LIMIT: 1028M
NEXTCLOUD_ENABLE_DRI_DEVICE: true # Intel QuickSync
SKIP_DOMAIN_VALIDATION: false # This should only be set to true if things are correctly configured.
TALK_PORT: 3478 # This allows to adjust the port that the talk container is using which is exposed on the host. See https://github.com/nextcloud/all-in-one#how-to-adjust-the-talk-port
volumes:
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer # This line is not allowed to be changed.