Nextcloud AIO webUI not being accessible

Yahgo0 · November 17, 2025, 9:12am

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
Operating system and version (e.g., Ubuntu 24.04):
- Ubuntu server 24.04
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?
- instalation/setup
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
- docker
Are you using CloudfIare, mod_security, or similar? (Yes / No)
- replace me

Summary of the issue you are facing:

[…] so I’ve been trying to set up the nextcloud AIO for about 3 days now I’ve had the same issue that i specify the ports 11000:80 and 8443:8443. inside my network the hosting server ip is 10.0.0.4 and i ssh into it from my WIN11 machine when setup the container and i look at the logs and it tells me

docker logs nextcloud-aio-mastercontainer
Trying to fix docker.sock permissions internally…
Creating docker group internally with id 988
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:

https://your-domain-that-points-to-this-server.tld:8443

/usr/lib/python3.12/site-packages/supervisor/options.py:13: UserWarning: pkg_resources is deprecated as an API. See Package Discovery and Resource Access using pkg_resources - setuptools 80.9.0 documentation . 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
[Mon Nov 17 08:38:11.085523 2025] [mpm_event:notice] [pid 150:tid 150] AH00489: Apache/2.4.65 (Unix) OpenSSL/3.5.4 configured – resuming normal operations
[Mon Nov 17 08:38:11.085567 2025] [core:notice] [pid 150:tid 150] AH00094: Command line: ‘httpd -D FOREGROUND’
[17-Nov-2025 08:38:11] NOTICE: fpm is running, pid 159
[17-Nov-2025 08:38:11] NOTICE: ready to handle connections
{“level”:“info”,“ts”:1763368691.1099007,“msg”:“maxprocs: Leaving GOMAXPROCS=4: CPU quota undefined”}
{“level”:“info”,“ts”:1763368691.1100607,“msg”:“GOMEMLIMIT is updated”,“package”:“github.com/KimMachineGun/automemlimit/memlimit",“GOMEMLIMIT”:11284228915,"previous”:9223372036854775807}
{“level”:“info”,“ts”:1763368691.1101043,“msg”:“using config from file”,“file”:“/Caddyfile”}
{“level”:“info”,“ts”:1763368691.1109595,“msg”:“adapted config to JSON”,“adapter”:“caddyfile”}
{“level”:“info”,“ts”:1763368691.112357,“msg”:“serving initial configuration”}

when i go to http or https://10.0.0.4:11000 or :8080 or 8443 i get a timed out screen

this is my yaml file for it

version: “3.9”

services:
nextcloud-aio-mastercontainer:
image: ghcr.io/nextcloud-releases/all-in-one:latest
container_name: nextcloud-aio-mastercontainer
init: true
restart: unless-stopped
volumes:

nextcloud_aio_mastercontainer:/mnt/docker-aio-config
/var/run/docker.sock:/var/run/docker.sock:ro
/mnt/data/nextcloud‑data:/mnt/nextcloud‑data
environment:
APACHE_PORT=11000
APACHE_IP_BINDING=0.0.0.0
NEXTCLOUD_DATADIR=/mnt/nextcloud-data
#SKIP_DOMAIN_VALIDATION=true
NEXTCLOUD_MEMORY_LIMIT=1024M
NEXTCLOUD_MAX_TIME=7200
ports:
“11000:80”
“8443:8443”
volumes:
nextcloud_aio_mastercontainer:

im also new to the self-hosting world so if i said something wrong or if i dont make sense i am sorry please bare with me im open to learn and seeing if anyone has any insights. also let me know any addition info needed to solve this problem

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.

emma_rose77 · November 17, 2025, 10:11am

It sounds like AIO is running correctly — the logs are telling you that the WebUI is only available on port 8080, not the ports you mapped.

So instead of trying to connect on 11000 or 8443, try opening:

http://10.0.0.4:8080

in your browser (make sure it’s http, not https).
AIO always exposes the setup interface on 8080 internally, regardless of the port mappings you choose.

If you do want to access it through different ports, you’ll need to adjust your docker run command so those ports map to 8080 inside the container, for example:

-p 11000:8080

Then you could access:

http://10.0.0.4:11000

But as long as the logs say “You should be able to access it on port 8080”, that’s the correct one to use.

jtr · November 17, 2025, 8:36pm

These do not look correct. Please see the docs or example Compose.

github.com/nextcloud/all-in-one

compose.yaml

main

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/nextcloud-releases/all-in-one:beta if you want to help testing new releases. See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel
    init: true # This setting makes sure that signals from main process inside the container are correctly forwarded to children. See https://docs.docker.com/reference/compose-file/services/#init
    restart: always # This makes sure that the container starts always together with the host OS. See https://docs.docker.com/reference/compose-file/services/#restart
    container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not work correctly
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the built-in backup solution will not work
      - /var/run/docker.sock:/var/run/docker.sock:ro # May be changed on macOS, Windows or docker rootless. See the applicable documentation. If adjusting, don't forget to also set 'WATCHTOWER_DOCKER_SOCKET_PATH'!
    network_mode: bridge # This adds the container to the same network as docker run would do. Comment this line and uncomment the line below and the networks section at the end of the file if you want to define a custom MTU size for the docker network
    # networks: ["nextcloud-aio"]
    ports:
      - 80:80 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
      - 8080:8080 # This is the AIO interface, served via https and self-signed certificate. See https://github.com/nextcloud/all-in-one#explanation-of-used-ports
      - 8443:8443 # Can be removed when running behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
    # security_opt: ["label:disable"] # Is needed when using SELinux. See https://github.com/nextcloud/all-in-one#are-there-known-problems-when-selinux-is-enabled
    # environment: # Is needed when using any of the options below
      # AIO_DISABLE_BACKUP_SECTION: false # Setting this to true allows to hide the backup section in the AIO interface. See https://github.com/nextcloud/all-in-one#how-to-disable-the-backup-section
      # APACHE_PORT: 11000 # Is needed when running behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else). See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
      # APACHE_IP_BINDING: 127.0.0.1 # Should be set when running behind a web server or reverse proxy (like Apache, Nginx, Caddy, Cloudflare Tunnel and else) that is running on the same host. See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md

This file has been truncated. show original

Yahgo0 · November 17, 2025, 9:46pm

Thank you Emma and Jay for the speedy response.

I’ve done what you both said but i still cant access it i tried accessing the webui thru

http://10.0.0.4:8080

like Emma said i get Connection was reset error in my browser. and for jay in my yaml file had the ports in quotations and also not the same ports as the example compose and still after that i get a

channel 3: open failed: connect failed: Connection refused

from my server when i try to access the webui. more context is that I’m running the AIO container inside a ubuntu server with no web browser. I don’t think that’s a problem because i can just use the server ip and port to access it right? i have also tried a ssh tunnel so i can use localhost:8080 on my WIN11 machine to access it but no luck

ssh -L 11000:127.0.0.1:11000 me@10.0.0.4

I’ve tried this with all the ports i could find and still nothing

version: "3.9"

services:
  nextcloud-aio-mastercontainer:
    image: ghcr.io/nextcloud-releases/all-in-one:latest
    container_name: nextcloud-aio-mastercontainer
    init: true
    restart: unless-stopped
    volumes:
       - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
       - /var/run/docker.sock:/var/run/docker.sock:ro
       - /mnt/data/nextcloud‑data:/mnt/nextcloud‑data
    environment:
       - APACHE_PORT=11000
       - APACHE_IP_BINDING=0.0.0.0
       - NEXTCLOUD_DATADIR=/mnt/nextcloud-data
       - #SKIP_DOMAIN_VALIDATION=true
       - NEXTCLOUD_MEMORY_LIMIT=1024M
       - NEXTCLOUD_MAX_TIME=7200
    ports:
      - 80:80
      - 8080:8080
      - 8443:8843
      - #"11000:80"
      - #"11000:443"
      - #"11000:8080"
      - #"8443:8443"

volumes:
  nextcloud_aio_mastercontainer: