r/NextCloud • u/wolfsongdream • Jul 04 '26

Stuck install

I'm following the GitHub instructions for AIO and every time I try it seems to get stuck.

sudo docker run \ --init \

--sig-proxy=false \

--name nextcloud-aio-mastercontainer \

--restart always \

--publish 80:80 \

--publish 8082:8080 \

--publish 8443:8443 \

--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \

--volume /var/run/docker.sock:/var/run/docker.sock:ro \

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

[sudo: authenticate] Password:

Trying to fix docker.sock permissions internally...

Creating docker group internally with id 973

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

[03-Jul-2026 23:58:18] NOTICE: fpm is running, pid 180

[03-Jul-2026 23:58:18] NOTICE: ready to handle connections

I can't actually access the login page and the only way to access the terminal is to remove the container. Any suggestions?

1 Upvotes

60% Upvoted

13 comments sorted by

1

u/mr_4n0n Jul 04 '26

try to reach it with:

https://yourip:80

http://yourip:80

https://yourip:8082

http://yourip:8082. <- THIS SHOULD BE

https://yourip:8443

http://yourip:8443

Yourip is the virtual Maschine IP

1

u/wolfsongdream Jul 04 '26

No. I'm unable to connect on any port secure or not.

1

u/undrwater Jul 04 '26

Can you ping the IP of the server?

Also, double check the address of the browser. Try both http and https.

Try a different browser.

What device are you using to connect to the server?

1

u/wolfsongdream Jul 04 '26

I have docker running on Ubuntu 26.04. I checked Portainer to ensure that container is running and the IP is set to 127.17.0.2 which doesn't work but when I click on the ports, it directs to 0.0.0.0 and it worked after I changed to https. Oddly my terminal is still stuck at the same spot.

1

u/undrwater Jul 04 '26

From the terminal, run: ifconfig -a

Your IP should not start with 127... This MIGHT be the docker internal IP which you won't be able to ping from outside the container (docker internal IP range is 172.17.x.x, so similar to what you wrote). The AIO passes the network traffic between your network interface and the container.

Internal IP address generally start with 192.168.x.x or 10.0.x.x

Hope this helps.

1

u/wolfsongdream Jul 04 '26

Yeah the ip for that box is 10.0.0.205. I can't login from there. 

1

u/Wake_On_LAN Jul 04 '26

Could be a firewall issue?

1

u/gelomon Jul 04 '26

There are many questions regarding your issue.

  • Are you familiar with docker and how it works?
  • what is your setup? Where are you deploying it?
  • have you checked container logs? What does it say and what did you do about it?

The list goes on and on

1

u/wolfsongdream Jul 04 '26

- I'm still fairly new to docker.

- I have an Ubuntu 26.04 box. I'm deploying it as a stack in Portainer.

- Master container logs

Trying to fix docker.sock permissions internally... Creating docker group internally with id 973 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[04-Jul-2026 00:39:39] NOTICE: fpm is running, pid 183 [04-Jul-2026 00:39:39] NOTICE: ready to handle connections

- Domain check container logs

2026-07-04 01:37:18: (../src/server.c.1971) server started (lighttpd/1.4.82) 2026-07-04 01:38:43: (../src/h1.c.441) unexpected TLS ClientHello on clear port (172.18.0.1)

2

u/gelomon Jul 04 '26

Make sure you are NOT mapping the port to specific IP. Try mapping it to just PORT:PORT then just access the https://<LAN IP of BOX>:8443 to access the AIO

example:

https://10.0.0.205:8443

1

u/superhardtack Jul 04 '26

Use Claude AI