'nextcloud-aio-nextcloud' takes forever upon first start

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, , , , ,
21

You know, that would make a lot of sense if that was the case here.

Client: Docker Engine - Community
 Version:    27.3.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.17.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.29.7
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 15
  Running: 15
  Paused: 0
  Stopped: 0
 Images: 20
 Server Version: 27.3.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 7f7fdf5fed64eb6a7caf99b3e12efcf9d60e311c
 runc version: v1.1.14-0-g2c9f560
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.1.0-18-amd64
 Operating System: Debian GNU/Linux 12 (bookworm)
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 62.02GiB
 Name: maskin
 ID: ea69b0b6-6436-43ab-add5-07c49f77bcb1
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

And just a whole bunch of

NOTICE: PHP message: 404 Not Found
Type: Slim\Exception\HttpNotFoundException
Code: 404
Message: Not found.
File: /var/www/docker-aio/php/vendor/slim/slim/Slim/Middleware/RoutingMiddleware.php
Line: 76
Trace: #......
# ...
# ...

Otherwise the start of it is:

Initial startup of Nextcloud All-in-One complete!
# ...
[29-Oct-2024 17:28:59] NOTICE: fpm is running, pid 186
[29-Oct-2024 17:28:59] NOTICE: ready to handle connections
[Tue Oct 29 17:28:59.256844 2024] [mpm_event:notice] [pid 180:tid 180] AH00489: Apache/2.4.62 (Unix) OpenSSL/3.3.2 configured -- resuming normal operations
[Tue Oct 29 17:28:59.256858 2024] [core:notice] [pid 180:tid 180] AH00094: Command line: 'httpd -D FOREGROUND'
{"level":"info","ts":1730222939.2610319,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1730222939.2616003,"msg":"adapted config to JSON","adapter":"caddyfile"}
22

Can you maybe for a test enable ipv6 and check if that improves things?

See https://github.com/nextcloud/all-in-one/blob/main/docker-ipv6-support.md

1 Like
23

I actually did that as a previous debugging test and after running
sudo docker network inspect nextcloud-aio | grep EnableIPv6
i get "EnableIPv6": true,

24

I see, so all containers have an internal ipv4 and ipv6 address?

25

Seems like it, for example docker inspect nextcloud-aio-nextcloud
tells me it has "IPAddress": "172.19.0.6" & "GlobalIPv6Address": "fd2c:888a:1309::6"

26

I am out of ideas then. But it looks like your issue might be connected to https://github.com/nextcloud/all-in-one/issues/5472#issuecomment-2437227506

27

Doesnt sound unreasonable for that to be the core issue.
But i absolutely adore all the help and your attempt to get this working.

Guess a ““solution”” is to just install nextcloud on its own outside of AiO and docker. But that feels like it would be a last resort ““solution”” since not having it in docker and together with AiO would suck.

But i guess maybe downgrading to like 9.6.x would maybe fix it since that issue reports it on 9.7.0+

28

This topic was automatically closed after 90 days. New replies are no longer allowed.