Hey guys,
I posted this and a bunch of info in the Nextcloud help forum https://help.nextcloud.com/t/nextcloud-aio-freezes-have-to-manually-stop-all-containers-to-get-it-responsive/165826/1
But i thought id plug it here too in case anyone has a solution… Tried all kinds of things but cant prevent nextcloud from timing out
Thanks guys!
I’ve never heard of Nextclouf AIO, do you have links?
For the RAM, the 200mb free and 7GB available, it’s because linux uses ram for caching things, but this ram used for cache can be freed right away when needed (this is the 7gb available)
If i’m not mistaken docker will take all the ram it needs.
In my personnal setup I use Portainer to manage things with a UI and Ive setup nextcloud with the Stacks functionnality of Portainer (it’s just multiple docker compose) and in the stack I have Nextcloud server and a Nextcloud mariadb database (and maybe something else ? I might be forgetting some things) have you tried setting up Newtcloud this way ? I suppose the AIO is bundled with the db and the server as one image?
I’ve never heard of Nextclouf AIO, do you have links?
Yeah i started off going the plain nextcloud and mariadb, but i saw somewhere on nextclouds github i think??? that said they reccommend using the AIO version, so i just did that. Might be worth just keeping it simple and doing nextcloud + mariadb
I had the same issue last week (was my first installation)
I managed reinstalling it after a purge, and now it works good. The only difference is now i did not activate server side crypt module. I’m running NcAIO on Debian 11.
I decided not to use server side encryption, as its just running on a comp at home. But maybe a fresh reinstall would work. Did you do anything special when purging?
https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance
After that, fresh install, no encrypt, everything ok.
Might have to try squeezing out a backup and giving it a go
Ehi, just to feed my curiosity, has it worked?
Was meant to get back to you, sorry
Didnt work for me unfortunately… maybe some setting in the backup was carried over and thats the problem. But i think the actual problem is hardware/setup based rather than config/software. Might invest in a less shit computer soon haha
Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: [email protected]
I just upgraded to that version and it’s now seemingly borked.
Docker compose down should stop them all as far as I know. Not sure about the timing out though, I think there may be some issues with this version of AIO.
