AIO Setup not loading up Talk, Colabora, Fulltextsearch

ℹ️ Support
, ,
1
Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

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:

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

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • Nextcloud Hub 9 (30.0.8)
  • Operating system and version (e.g., Ubuntu 24.04):
    • Debian GNU/Linux 12 (bookworm) 64 Bit
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • after install
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • AIO via Github-Command
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

Im new to Docker so it might be a small problem thats causing my struggle.
Ive had an Nextcloud instance working but wanted to switch to the AIO for more simplicity. So I installed a new SD Card for my Pi (Lite, 64 bit) and installed Docker via the command in the instruction on Github.
Afterwards I installed my Nextcloud with the following additional commands:

sudo docker run \
--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 /var/run/docker.sock:/var/run/docker.sock:ro \
--volume /media:/media \
--env NEXTCLOUD_MOUNT="/media/" \
--env NEXTCLOUD_UPLOAD_LIMIT=150G \
--env NEXTCLOUD_MAX_TIME=7200 \
--env NEXTCLOUD_MEMORY_LIMIT=3G \
--env FULLTEXTSEARCH_JAVA_OPTIONS="-Xms1024M -Xmx1024M" \
nextcloud/all-in-one:latest

the Installation worked and i could reach myip:8080 for the container config. There i chose: Collabora, Fulltextsearch, Imaginary, Nextcloud Talk and Whiteboard.

After a couple of minutes i was able to reach my Nextcloud through the Domain. But Talk, Fulltextsearch and Collabora are not installed.

The logs from these are pretty full and i have no clue what to look for.
In every Video-Tutorial it works instantly without any further configuration.

Ive redone this like 3-5x now and never got it running.
Wether i choose NC Hub 9 or 10

Log entries

nextcloud-aio-nextcloud: 2025-03-30T15:44:53.246960978Z Connection to nextcloud-aio-database (172.18.0.5) - Pastebin.com
nextcloud-aio-collabora (end): https://pastebin.com/48qQm3Ad
nextcloud-aio-talk: 2025-03-30T15:38:58.739379851Z ++ hostname ++ grep -oP '[0-9]+\.[0-9]+\.[0-9]+\. - Pastebin.com
nextcloud-aio-fulltextsearch: 2025-03-30T15:42:00.545162322Z CompileCommand: dontinline java/lang/invoke/Metho - Pastebin.com

nextcloud-aio-collabora is too much for Pastebin so here is start and end…
nextcloud-aio-collabora (start): 2025-03-30T15:38:44.548434257Z wsd-00007-00007 2025-03-30 17:38:44.548121 +0200 - Pastebin.com
nextcloud-aio-collabora (end): https://pastebin.com/48qQm3Ad

Nextcloud Logfile Download

Web server / Reverse Proxy

Due to a fresh install there should not be any Reverse proxy or something.
I just got an service that redirects my public ipv4 to kellercloud.any64.de
Thats it.

I really hope you can help me and I am just missing a single thing.
But I dont get it right now…

2

Hi, after enabling all these additional optional containers, did you click on the Save changes button below the options as described in the AIO interface?

3

Yes I did. They even showed green and I can see that they have started (on my pi and through the interface (green status and logs).

But something is not working. It often says that curl didn’t work for a specific .tar but I have no clue why It shouldn’t work.

Just for clearance: I’m not using a reverse proxy am I?

4

Hi, I’ve carefully gone through your posts in this thread and would like to share my opinion.

From what you’ve described, it seems you’re trying to install Nextcloud AIO on a device that is likely not suitable for this kind of deployment. This is based on several facts you’ve mentioned:

  • You’re using a Raspberry Pi or a similar ARM-based device, which has significantly limited performance and RAM capacity.
  • Most importantly, you’re using an SD card as the storage medium, which is by far the worst possible choice for a setup like this. SD cards are extremely slow, unreliable for constant read/write operations, and tend to degrade quickly under such workloads. This alone can cause serious instability and failed service startups.
  • You’re having issues loading services like Talk, Collabora, and Fulltextsearch – all of which are resource-hungry components that require substantial memory, CPU power, and fast disk I/O.
  • The AIO Dashboard itself fails to load properly, which is a strong sign of insufficient resources or architectural limitations (ARM vs. x86_64).
  • You also mentioned you want to run everything on a single device, but that’s a tough challenge with AIO, which consists of multiple Docker containers, each with its own demands.

My opinion:
Nextcloud AIO is designed for more capable hardware, ideally with an x86_64 architecture, at least 6–8 GB of RAM (12–16 GB recommended), a multi-core CPU, and most importantly, a reliable SSD or NVMe drive – not an SD card. ARM boards like the Raspberry Pi are okay for basic Nextcloud setups, but AIO is not meant to run in such a constrained environment.

Correct me if I’m wrong — but based on everything shared, the main issues seem to stem from hardware limitations and the use of an SD card.
If you want to run AIO with a stable experience, I highly recommend switching to a more powerful setup, such as a mini PC with an Intel CPU, SSD storage, or a VPS, where you’ll have the reliability and performance needed for all AIO services to run smoothly.

1 Like
5

Hey Vawaver,

first of all thanks for your really detailed response!
I mean this could for sure be a solution but I have seen multiple posts and videos where AIO was installed on a Pi. I’ve got a Pi4 8GB and only my Linux OD is on an 256gb SD Card.
My data will be stored on a 4TB SSD.

I also checked htop and even on boot it looked alright (70-80% usage on cpu and 30% on Ram…

Maybe I’ll just go back to Nextcloudpi and install everything by myself… :frowning:

1 Like