Happily using NextCloud AIO without any major issue.
Installed Nextcloud-AIO using the docker script, took about 4 - 5 terminal commands. Practically zero issues! Hopefully someone else can provide some help in the thread!
Do you have office set up in it?
I have it set up. Try the AIO docker image. Once you get it set up, it pretty much just works. You just pick which office suite you want, check a few optional features if you want 'em, and it handles the rest for you. Most importantly, the AIO image is from nextcloud. They test it, it always works because it is the blessed version from them. If you’re not a Linux guy, don’t try the other installation methods, they’re much, much more difficult.
I’ll give it a shot. I’ve tried so many different approaches already. I think I maybe tried to install AIO straight onto a linux vm; don’t recall how it got derailed. I did build a Lubuntu VM for experimentation. I really wanted to get an Ollama chatbot running to assist me in my future digital endeavors, but it just wouldn’t come together.
I’ve just finally and fully spun down a proxmox server I’ve been running and updating as my home lab for six years.
Every major update seemed to break something. Upgrades were always a roll of the dice as to whether it would even boot. It’s probably at least partially my fault for using an old R710 and running docker directly on the OS instead of within a container, but it was still by far my least reliable piece of kit.
The last
apt updateremovedsudo, and I can’t be arsed to rebuild, so I’ve moved the critical bits to a fleet of SBCs. Powering that fucker down was a huge relief.I’ve setup Nextcloud but have done next to nothing with it.
My Lemmy instance gives me the most problems, but it’s also the only publicly available service I run. Mostly the issue is it seems to have a memory leak that forces me to restart it every few days.
Everything else has been completely rock solid for me, running on a mini pc (formerly a pi4 until I wanted to start doing stuff with Jellyfin and needed more power for transcoding) on OpenSUSE Leap all in docker containers. Makes it insanely easy to move stuff. I had no issues basically just copying the docker-compose files and data and bringing them up even when switching architectures.
I run it and mariaDB in docker and they run perfectly when left alone, but everything breaks horribly if I try to do an update. I recently figured out that you need to do updates for NC in steps, and docker (unRAID’s, specifically) defaults to jumping to the latest version. I think I figured out how to specify version now so fingers crossed I won’t destroy it the next time I do updates.
This is probably what I’m doing wrong. I’m using linuxserver’s docker which should be okay to auto update, but it just continuously degrades over time with updates until it becomes non-functional. Random login failures, logs failing to load, file thumbnails disappearing, the goddamn Collabora office docker that absolutely refuses to work for more than one week, etc.
I just nuke the NC docker and database and start from scratch every year or so.
Yeah I don’t like auto upgrades. Everyone says it’s fine but that’s not my experience.
My stuff isn’t public facing so I’m not worried about 0-days
You absolutely need to move from patch to patch and cannot just do a multiple version jump safely. You also need to validate the configs between versions, especially major release updates or you risk breaking. New features and optimizations happen and you also may need to change our update your reverse proxy configuration on update, or modify db table configuration (just puking this from memory as I’ve had to do it before). I don’t know that there’s automation for each one of those steps.
Because of that, I run nextcloud in a VM and install it from the binary package. I wrote a shell script that handles downloading, moving the files, updating permissions and copying the old config forward, symlinking and doing the upgrade. Then all I have to do is log in as administrator, check out the admin dashboard and make sure there aren’t new things I have to address in the status page. It’s a pain, but my nextcloud uses external db and redis and PHP caching so it’s not an easy out of the box setup. But it’s been solid for a long time once I adopted using this script.
Would love to take a look at that bash script (or at least a template of it) if you wouldn’t mind
Sure! I’ll respond with a link in a bit.
Here you go:
There could probably be some additional refactoring here, but it works for my setup. I’m using default nginx paths, so they probably look different than other installs that use custom stuff like /var/www, etc.
Use it by putting it in a shell script, make it executable, then call it:
sudo scriptName.sh 28.0.1Replace the version with whatever version you’re upgrading to. I would highly recommend never upgrading to a .0, always wait for at least a .1 patch. I left some sleeps in the when I was debugging a while back, those are safe to remove assuming it works in your setup. I also noticed some variables weren’t quoted, I’m not a bash programmer so there’s probably some consistency issues that could be addressed if someone is OCD.
Thank you for taking the time ! This is a great resource
For me everything works fine since years, EXCEPT collabora. I use onlyoffice now, it’s much faster and very stable
I dunno what you guys are doing that makes your nextcloud die without touching it. Mine runs happily until I decide to update it, and that usually goes fine, too. I don’t use docker for it, tho.
I dunno what you guys are doing that makes your nextcloud die without touching it
Mine runs happily until I decide to update it
I swear every update ends up breaking it and putting it into maintenance mode for me. This would then lead to 1-2 hours of going through previously visited links to try and figure out what fixed it previously. For me personally, it seems like it’s usually mariadb requiring a manual update that fixes it but it’s always a little scary.
I always run
occ upgradeandocc db:add-missing-indicesafter a package upgrade, just to be sure that I do not miss any database migrations. Using Archlinux I wrote a pacman hook so that it happens automatically.
Just dont update it then
It’s the containerization causing this imo. I also host nextcloud on bare metal and it’s quite stable
I’ve been reading nextcloud forums/reddit/lemmy/etc. for years now, and i feel like 90% of the problems are from people using docker or whatever easy one-click solution is out there
I’ve been running NC the old fashioned way for years now and i’ve never had problems of NC dying for no reason.
Have i had issues? Of course… Not not like the ones people keep coming here and shitting on NC
The only times i’ve had major issues and it was actually a problem with nextcloud, is buggy major version releases… So i never install a new major release until X.0.1 these days. Havent really had problems since
The new Linuxserver.io docker image at the very least has solved the annoying update cycle NextCloud has and seems to have fixed the need to do that every few months. I haven’t ever had it die but I don’t push it hard and I keep the plugins to a minimum because I just don’t trust it and it doesn’t run all that well.
When I first deployed Nextcloud, it was just like this. Random crashes, lockups, weird user signin issues, slow and clunky.
But one day it just started working and was super stable. I didn’t do anything, still not sure what fixed it lol.
Only complaints I have with Nextcloud are that it’s slow and updates suck over the web interface. But apart from that it has been reliable. I’m not running it through Docker. In fact, my installation is so old that the database tables still have an
oc_prefix.You might want to try migrating your nextcloud instance to postgres instead of mysql/mariadb. Many people says they get some big performance boost. I’m going to try it myself next weekend to see if it’s true.
They don’t anymore? XD
+1 this is exactly my experience. My install must be 5-6 years old at this point and its on the rails. I’ve braved many php updates…
Mine is a snap install that started 3 years ago on virtual box and was ported over to proxmox. It has never broken, updates automatically, and generally seems to work just fine.
It doesn’t load instantly, but it doesn’t drag by any means.
Nextcloud has been super solid for me using the official docker image.
This has been a serious concern of mine. In the event that I prematurely die I have everything set up with automatic updates, so that hopefully my family can continue to use the self-hosted services without me.
Nextcloud will not stop shitting the bed. I’d give it a few months at most if I died, at which point my family would likely turn back to Google Drive.
I’m looking for a more reliable alternative, even if it’s not as feature-rich.
The way that they do updates doesn’t make automated updates very easy. There are usually a few little nagging things that have to be done or changed and they don’t always seem to be the same. I just update manually and make sure I’ve got a good backup of all my family’s files.
If you’re ok with just file storage sftpgo has been solid for me for years now. Does sftp ftp and WebDAV (like nextcloud). Webui isn’t as pretty but it’s fast. Mobile apps will be various sync apps with sftp or WebDAV support. On Android folder sync pro is pretty good for keeping documents and pictures backed up
I’ve told my wife and family that if something happens to me, they need to start migrating all their stuff off my self-hosted services to cloud services because its a matter of time before something fails and nobody’s around who knows or cares to fix it.
You don’t want your kids using a rope, so keep them away from linux.
My oldest kid is a senior in highschool and is starting to show some interest in Linux and this kind of stuff. I’m hopeful that I can change my tune soon and maybe have one of the kids to share a hobby with!
For years, I had an unstable unraid server. I was fixing it every couple of days after a lockup. I had decided that unraid sucked. When it was up for a week I celebrated. Every one of my dockers was a suspect. I learned to hate all of them.
Then I shitcanned the next cloud docker.
Been up for months without a hiccup.
I really don’t understand all those posts: I use nginx, apparmor, partially even modsecurity, I use collabora office official debian package, face recognition, email, update regularly (waiting for major upgrades for every app I use to be updated), etc. and literally never had a problem in the last 5 years except for my own experiment. True, only 5 people use my instance, but Nextcloud is rock solid for me
Likewise. I have been running it for years, almost no problem that I can think of. My setup is pretty vanilla, Apache, MySQL. It’s running in a container behind a reverse proxy. I keep it as up to date as possible. Only 3 people use mine, and I don’t use very many apps: files, notes, bookmarks, calendar, email.
I was trying for the 3rd time to install the collabora office app in nextcloud. I think it’s hilarious they know it’s going to time out and they give you a bogus command to run to fix it. So unnecessarily irritating.
In my own personal experience, Nextcloud;
- Needs constant attention to prevent falling over
- Administration is a mess
- Takes far too long to get used to its ‘little ways’
- Basics like E2EE don’t work
- Sync works when it feels like it
- Updating feels like russian roulette
Updating from my experience is not Russian roulette. It always requires manual intervention and drives me mad. Half the time I just wget the new zip and copy my config file and restart nginx lol.
Camera upload has been fantastic for Android, but once in a while it shits its brains out thinking there are conflicts when there are none and I have to tell it to keep local AND keep server side to make them go away.
The update without fail tells me it doesn’t work due to non-standard folders being present. So, I delete ‘temp’. After the upgrade is done, it tells me that ‘temp’ is missing and required.
Other than that it’s quite stable though… Unless you dare to have long file names or folder depths.
This could be it, but I also remember reading once it might be something to do with php.ini timeout settings too
It’s like…having a toddler LMAO my little digital toddler lololol
Never had a single functional problem with Nextcloud, other than the fact that it’s oppressively slow with the amount of files I’ve shoved into it. Mind you I also don’t use MySQL/MariaDB which I consider a garbage-tier DB. Despite Postgres not being the “Recommended DB” for Nextcloud it works perfectly for me. Maybe that’s the difference.
Postgres is the standard db in the AIO container nextcloud has put out as their standard.
