this post was submitted on 13 Mar 2024
46 points (79.5% liked)

Selfhosted

40296 readers
225 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I've enough.

Last year the automatic updater was rebooting windows without any warning after the uac prompt. The problem continued for months before being fixed

This year I got an update a week. Very annoying to get the same "why u no reboot? I need updates" question every single time I turn on my PC.

Today when updating it kills explorer.exe without any confirmation and doesn't bring it back to life.

I don't think that their paid enterprise customers are doing the ~~beta~~ alpha testers like this. Is it really necessary to push nightlies to end users? It can't be tested casually for a couple of days then pushed?

I disabled the updates check and will update the nextcloud desktop client manually every 5 years if I can remember. Added an exception to Winget so it doesn't update it. I lost my patience.

you are viewing a single comment's thread
view the rest of the comments
[–] mranderson17@infosec.pub 41 points 8 months ago (4 children)

Ok, I'm prepared to be downvoted today so here goes.

Nextcloud is an enterprise cloud suite. The one you run in docker on your rpi (or whatever) is the same one that is run at a company, albeit with more high availability and redundancy, but the same application, proxies, caching, db, etc. Nothing is stopping you from running the stable channel and testing your upgrades, or even rolling out specific stable client versions to your devices.

Said companies often have teams (more than one person) to run it, stage upgrades, automated testing, automated backups, monitoring, etc. They go to work and do just that, maybe not every day but at least a couple times a week their focus is Nextcloud and only Nextcloud.

What many people in the self hosting community do is spin up docker, without ever having touched docker before, and try to run Nextcloud, forget that it exists, and then upgrade it a year later across multiple versions without maintaining the database. Then they obsess about how fast an app loads by refreshing it a whole bunch, and then complain on internet forums that it sucks. This, like many posts, doesn't have a specific problem for us to help with, no logs or stack traces have been posted, and the subject of the complaint shows just how terrible your understanding of application security is.

So, while there is legitimate criticism of some of Nextcloud's design choices, this isn't it. And at the risk of sounding a little gatekeepy, if you post "nextcloud updates break everything" with no context you probably should spend some time gaining a better understanding of how internet facing services work and make an attempt to fix the problem (probably misconfiguration, and in this desktop client case probably a heap of un-updated local software installed alongside the client), which I'm sure people would find if they did the bare minimum of reading a few log files or any of the other things that come with being an application admin.

[–] simon574@feddit.de 21 points 8 months ago (1 children)

Wasn't OP complaining about the Windows desktop client? What has that to do with the server setup, Docker, etc? People can have the exact same issues on the client side even if the Nextcloud instance is professionally managed by a large organization.

[–] mranderson17@infosec.pub 1 points 8 months ago* (last edited 8 months ago)

I mentioned the client in there (4th paragraph), but mine was more of a general rant on the overall low effort that seems to have been put in to figuring out what the actual problem was. And that it is relatively common among people in the self hosting community to assume that Nextcloud is a lot simpler than it is. It's a huge cloud suite consisting of many applications, clients, plugins, proxies, caching, database, etc. You need to have a pretty good understanding of how it all works, and how to investigate a problem, and ideally you should be testing before upgrades. Large organizations often even test endpoint applications like the desktop client and push out only tested versions to users via policy or some kind of endpoint management.

I can't really draw many conclusions from the very little information provided in this post, but I suspect OPs windows machine is not in an entirely stable state, which is what is causing some of these update issues.

And, I put some of the blame for Nextcloud under-representing it's complexity on Nextcloud's marketing and AIO. You absolutely can install it without understanding anything, and that's a little dangerous in my opinion because it is actually quite complex and you will probably end up breaking it at some point and need to dig in to fix it.

load more comments (2 replies)