No if I have to keep fixing it , it is not worth my time.
I installed owncloud years ago and came to the same conclusion and just got rid of it. I use syncthing nowadays though its not the same thing.
Yep, I’ve adapted all of my setup to syncthing, and never looked back.
Any guidance on this? I looked into Synthing at one time to backup Android phones and got overwhelmed very quickly. I’d love to use it in a similar fashion to NextCloud for syncing between various computers too.
Well, it works in a different way than NextCloud. You don’t have a server, instead you just make a share between your computers and they are all peers.
It takes some getting used to the idea, but it’s actually much simpler than NextCloud.
So if I wanted to sync photos from my phone to the computer, then delete the local copies on my phone to save space, that would not work?
E: But keep the copies on the computer, of course
You would have to move them into some folder you are not syncing.
It really wasn’t all that complicated for me. Install the client on two devices set a share up on one device go to the other device Hit add device put the share ID in. Go back to the first devices admin and say allow the share
I was very intimidated as well, I’ll try to simplify it, but as always check the documentation ;)
This is the process I used to sync between my Windows PC and Android phone to sync retroarch saves (works well, would recommend, Pokemon is awesome) I’ve never done it on a Linux, though i assume it’s not too different
https://docs.syncthing.net/intro/getting-started.html
I downloaded the Synctrazor program so that it would run in the tray, again I’m not sure what the equivalent/if this would be necessary on Linux.
No shade to the writers, but the documentation isn’t super noob friendly, as I figured out. I’d recommend trying to cut out all the fluff, and boil it down to bare essentials. Download the program (whichever one seems right for your device, there’s an app for Android) and follow the process for syncing stuff (I believe I used a video guide, but it’s not actually as complicated as it seems)
If you need specific help I’d be happy to answer questions, though I only understand a certain amount myself XD
I’m absolutely at that point with Nextcloud. I kind of didn’t want to go the syncthing route, but I’ll probably give it a shot anyway since none of the NC alternatives seem any better.
I tried nc it for a while I would have taken me till the end of days to import all of my files.
I suspect I could keep it running by doing lockstep backups and updates. But it was just so incredibly slow.
I just want something that would give me remote access to my files with meta information about my files and a good search index.
Pydio Cells/Seafile?
I’ll look at those ASAP, super hopeful
i have been running the new owncloud (ocis) and, with some quirks and very basic functionality, it’s been running for 2+ years and survived multiple updates without major complications
Came to same conclusion too
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
Am i the only one left who doesn’t want a snap docker Kubernetes container and just installs nextcloud in a normal way and never had any problems?
Same here. I’m just installing it normally, and my nextcloud instance is just chugging along.
For me it’s the opposite. I tried to use nextcloud for years, installing the normal way, and it always broke for no reason. I just started using it on docker and it has been perfect, fingers crossed.
Interesting, when I used docker on a proxmox build, it would give me trouble. Once I installed it the normal way on an Ubuntu build, it was good to go.
I wonder why that is?
Fingers crossed that it continues to work for you in the current configuration!
Because when you’re using Docker, you shouldn’t use Proxmox. And to be fair, I don’t understand why people are using Proxmox at all.
I used Proxmox because it was free and open source with backup tools integrated into the system.
Same here, but after v25(?) it won’t update on my RPi 4 any longer, think they went 64 bit only?
Other than that no issues
None. I don’t make a habit of keeping “misbehaving” apps around. If I can’t get to the bottom of a specific issue that app is getting the boot from my stable.
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.
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.
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!
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
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.
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.
I have nextcloud running since nearly 5 years and it never failed once. Only dowtime is when the backup fails and somehow maintenance mode is still enabled (technically not a crash)
For those interested: Running in docker with mariadb in a stack, checking updates with watchtower everyday and pulling from stable, backups with borg(matic)
++same
Docker:nextcloud+mariadb+caddy
I’ve been running nextcloud since before it was nextcloud. Was owncloud then moved to next cloud.
Another user put it best. It always feels 75% complete. Sync isn’t fast, gives errors that self correct when restarting the all. Most plugins are even more janky or feel super barren.
I wanted to like it so much but I stopped being able to trust most plugins which meant I had dedicated apps for those things and used nextcloud only for file sync.
If you only want file sync then seafile is vastly superior so that’s what I now have.
Sounds like a common software issue. All the features where developed to 80%, and then moved on to the next feature. Leaving that last, difficult, time consuming, 20% open and unfinished.
It’s the difference between more corporate or Enterprise projects and FOSS projects in a lot of ways. Even once that project matures and becomes a more corporate product the same attitude towards completeness and correctness tends to persist.
(not saying foss is bad, just that the bar tends to be lower in my experience of building software, for many legitimate reasons).
It’s “cultural” in a way depending on the project.
LibreOffice wants to call with broken rendering on Windows, but the changelog mentions new tasty features. But FOSS can do it, Debian can. Those project managers should learn from their approach, whatever it is.
Yeah, I wish Nextcloud focused more on the file manager side of their applications. I was using it on my TrueNAS instance and it seems like an unfinished product. E2EE is not enabled by default and looks like their implementation is not perfect either.
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.
This is ultimately why I ditched Nextcloud. I had it set up, as recommended, docker, mariadb, yadda yadda. And I swear, if I farted near the server Nextcloud would shit the bed.
I know some people have a rock solid experience, and that’s great, but as with everything, ymmv. For me Nextcloud is not worth the effort.
If all you want is files and sharing try Seafile
That’s what I’ve got running now, and for me Seafile is been rock solid.
Nextcloud has been super solid for me using the official docker image.
Same with my arch install, didn’t touched it for 2 months even though laptop was turned off it decided to die when i launched it and run pacman -syu
I regularly “deep freeze” or make read-only systems from Raspberry Pi, Ubuntu, Linux Mint LMDE and others Linux Distros whereas I disable automatic updates everywhere (except for some obvious config/network/hardware/subsystem changes I control separately).
I have had systems running 24/7 (no internet, WiFi) for 2-3 years before I got around to update/upgrade them. Almost never had an issue. I always expected some serious issues but the Linux package management and upgrade system is surprisingly robust. Obviously, I don’t install new software on a old system before updating/upgrading (learned that early on empirically).
Automatic updates are generally beneficial and helps avoid future compatibility/dependency issues on active systems with frequent user interaction.
However, on embedded/single purpose/long distance/dedicated or ephemeral application, (unsupervised) automatic updates may break how the custom/main software may interact with the platform. Causing irreversible issues with the purpose it was built for or negatively impact other parts of closed circuit systems (for example: longitudinal environmental monitoring, fauna and flora observation studies, climate monitoring stations, etc.)
Generally, any kind of update imply some level of supervision and testing, otherwise things could break silently without anyone noticing. Until a critical situation arises and everything break loose and it is too late/too demanding/too costly to try to fix or recover within a impossibly short window of time.
This got mee googling Nextcloud and I think I’m going to give it a try 😱
Seriously homie, unless you’re a fucking linux docker nerdshit wizard, you should find another way.
Thanks for the warning 🙂 Sometimes I still think I have as much spare time as 10 years ago 😉
You could be a legless NEET and not have enough time to get this fucking bullshit to work correctly.
The problem child for me right now is a game built in node.js that I’m trying to host/fix. It’s lagging at random with very little reason, crashing in new and interesting ways every day, and resisting almost all attempts at instrumentation & debugging. To the point most things in DevTools just lock it up full stop. And it’s not compatible with most APMs because most of the traffic occurs over websockets. (I had Datadog working, but all it was saying was most of the CPU time is being spent on garbage collection at the time things go wonky–couldn’t get it narrowed down, and I’ve tried many different GC settings that ultimately didn’t help)
I haven’t had any major problems with Nextcloud lately, despite the fragile way in which I’ve installed it at work (Nextcloud and MariaDB both in Kubernetes). It occasionally gets stuck in maintenance mode after an update, because I’m not giving it enough time to run the update and it restarts the container and I haven’t given enough thought to what it’d take to increase that time. That’s about it. Early on I did have a little trouble maintaining it because of some problems with the storage, or the database container deciding to start over and wipe the volume, but nothing my backups couldn’t handle.
I have a hell of a time getting the email to stay working, but that’s not necessarily a Nextcloud problem, that’s a Microsoft being weird about email problem (according to them it is time to let go of ancient apps that cannot handle oauth2–Nextcloud emailer doesn’t support this, same with several other applications we’re running, so we have to do some weird email proxy stuff)
I am not surprised to hear some of the stories in this thread, though. Nextcloud’s doing a lot of stuff. Lots of failure points.
