The Longstanding Nightmare of Nextcloud's Update Process

This post was flagged by the community and is temporarily hidden.

> Your post was flagged by the community.

My post has been flagged by the community, reflecting how Nextcloud typically responds to criticism. I assure you, I wasn’t in breach of any rules. This seems like pure censorship for bringing up inconvenient themes…

I would suggest that your tone is just not very friendly to the volunteers who try to help fellow home users here. There is also nothing useful that you add, nor ask. Criticism is fine if it’s constructive, yours isn’t constructive in any way.

I get your irritation - but I would also like to point out that, with about half a million Nextcloud servers out there using the craziest kinds of hardware and software combinations, just cosmic rays causing random bitflips alone will already ensure that probably half a dozen of them break on every upgrade. It’s just a sad numbers game.

This step didn’t go wrong for the very vast majority of systems, so it is definitely not a design issue. It’s either a weird setup thing, something that recently broke, a mistake you made, or just plain bad luck. See if the file that it needs/asks for exists, if not, check where it is, and if it is properly readable and write-able.

Good luck, and try to breathe a bit next time before you ask for help.

Alright, enough with the “poor developer” rhetoric. What should I do? Pat them on the back and say “great job”? Nextcloud is a multimillion-dollar company, proudly waving the flag of open source, all about community and so on. But the reality is that non-paying users are handed sub-par pieces of software, especially when it comes to updates.

I didn’t offend anyone and I was honest in my review. The update process stinks and needs to be greatly improved and revised.