Selfhosted

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.

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.

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

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?

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.

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.

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 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.

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 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

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.

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)

Always works great for me.

I just run it (behind haproxy on a separate public host) in docker compose w/ a redis container and a hosted postgres instance.

Automatically upgrade minor versions daily by pulling new images. Manually upgrade major versions by updating the compose file.

Literally never had a problem in 4 years.

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!

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.

Nextcloud has been super solid for me using the official docker image.

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.

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.

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'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 update removed sudo, 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.

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.

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.

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

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

10 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.

[Thread #392 for this sub, first seen 1st Jan 2024, 02:35] [FAQ] [Full list] [Contact] [Source code]

The solution for me is that I run Nextcloud on a Kubernetes cluster and pin a container version. Then every few months I update that version in my deployment yaml to the latest one I want to run, and run kubectl apply -f nextcloud.yml and it just does its thing. Never given me any real trouble.

Dude- it's like you're reading my mind. I've installed Nextcloud 4 different times, the most recent being on docker desktop in Win11. I've resorted to using chatgpt to help me with the commands. LITERALLY EVERY STEP RESULTS IN AN ERROR. The Collabora office suite (necessary to view or edit cloud docs without downloading them) WILL NOT DOWNLOAD. The "php -d memory_limit=512M occ app:install richdocumentscode" chatgpt and Nextcloud suggest is not recognized by the terminal. You can't just download Collabora, cuz fuck you, i guess, and you can't access Docker's actual file system from windows explorer.

I've typed nonsense into various black screens for upward of 20 hours now, and nextcloud is "working" locally. I can access my giant hard drive from my android nextcloud app, but it's SLOW AS FUCK.

I can't imagine how many man-hours it would take to open the server to the internet. Makes me want to fucking barf just thinking about it.

I've been fucking with Linux since 2005 and have yet to get a single thing to work correctly. I guess I'm the only one who thinks an (mostly) invisible file system in incomprehensible repetitive folders, made of complete nonsense commands might not be the best way to operate a computer system.

I'm really frustrated if you can't tell.

On another topic, trying to get Ollama to run on my Lubuntu VM was also impossible. I guess if everyone knew it was going to force you to somehow retroactively configure every motherfucking aspect of the install nobody would bother. You can sudo all day and it still denies me permission to do things LISTED IN THE MOTHERFUCKING DOCUMENTATION.

Is this all just low-effort poorf** bullshit that doesn't actually work?

I've been updating Nextcloud in-place (manually) for multiple major versions without any flaws. What is the problem?

Well... no... I have been self hosting it for several years over multiple major versions now. Only for Files, Calendar and Deck though. It was a bit hard to set up, but reading the general Apache and PHP documentation helped a lot.

Perhaps ironically, lemmy. I had the database catastrophically fail early on, and ever since then federation has been broken with most major instances. I kind of prefer lotide anyway, much more minimalistic, less of a focus on upvotes and downvotes, and the code base is simply enough that I've been able to hop into it and make changes.

This got mee googling Nextcloud and I think I'm going to give it a try 😱

The only device running Snap in my house is a Raspberry Pi running the Snap Nextcloud and it's rock solid.

This might be a deployment issue. How are most people running it?

I can’t remember the last time I laughed this much