I’m still too container stupid to understand the right way to do this. I’m running it in docker under kubernetes and sometimes I don’t update nextcloud for a long time then I do a container update and it’s all fucked because of incompatible php versions of some shit.
I don’t remember much about how to use kubernetes but if you can specify a tag like nextcloud:28 instead of nextcloud:latest you should have a safer time with upgrades. Then make sure you always upgrade all the way before moving to a newer major version, this is crucial.
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.
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.
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.
This is Seafile for me. Definitely not the “set it and forget it” Google Drive alternative I was hoping for. Thank goodness I have Syncthing backing up important files, but sharing with friends and family is a nuisance.
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.
If you’re giving those companies personal info (name, phone, address, CC) they can track you regardless of what emails you use with each of them.
And if you’re not giving them personal info I don’t see how that works. Yeah so I register on both random site A and random site B with aliases @tfyuhegddssgvd.com, so what? How are they going to find out about each other? What will they tell each other even if they did? And why risk a GDPR violation for such silly reasons?
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.
I had TOTP die for one user on my Nextcloud. I tried to disable it, but it “didn’t exist”. I tried to enable it, but it was already enabled. It would come up when I used occ twofactorauth:state user. I ended up fixing it by (force) disabling the app and re-enabling it. It didn’t break any other user’s TOTP and it fixed problem-user’s TOTP. No idea what went wrong, but I get these random issues with Nextcloud sometimes.
The plus side to this is I’ve learnt how to use Mariadb and I’ve gotten better at debugging things.
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)
Proton is in the process of removing their PC bridge in favor of a custom app. After they’re done you won’t be able to migrate your email away from their service anymore.
Which is ironic, when people are trying to flee from Google. Out of the fire and into the frying pan…
It’s in restricted beta currently, only available to a small category of users, and still lacking features. They say it will launch early 2024 but it looks more like mid-year to me (at best).
Point is, it won’t happen very soon, but it will happen
For YouTube, it’s probably not possible to not use its content, but you can try alternate front ends like Piped (and its wonderful Android client, LibreTube, if you’re on Android.)
For Gmail, not sure if this works for you but I set the vacation feature to reply to every email I receive notifying them of my new email. I switched to Vivaldi Webmail (Proton doesn’t let you use 3rd party clients w/o a subscription plan btw, I’d switched to Vivaldi first so not a major thing for me) but Skiff (paid) looks good, Kagi Search is planning an email service, Tutanota has an email service, and I guess you could self host. While you transition, use a client that lets you have a unified inbox (K9 works on Android) and just have both logged in.
The only thing i have done so far is use imap into thunderbird…. All this is valuable. I want to use a self hosted solution but at the moment its all a surface level thought. Thanks a lot for this comment!!
Weird. I’ve had a Pi-Hole + Unbound running on a Pi Zero since 2018 and it’s never had any issues. I expected the Zero to kinda suck but it has been nothing but smooth sailing. It gets USB power from my router and even if my router reboots the Pi also auto reboots itself.
I do next to no maintenance on it and it just keeps on chugging along. Maybe once every six months or so I SSH in and do a pihole -up and that’s it.
I’m not self hosting an instance, but kbin is super fucking broken lately and it’s getting really frustrating. It’s been about a week. I submitted a ticket in their Git repo, but no response.
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.
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.
Well dang, I have Nextcloud installed as a snap (which has been perfectly stable for me when running on Ubuntu Server), but I was thinking of switching over to a docker installation; this thread doesn’t exactly fill me with enthusiasm for that idea…
Anecdotal, but Ive had a container running Nextcloud in an LXC on Proxmox along with PiHole, Step CA, Bacula, and quite a few other services and I’ve had zero downtime since June 2023. Even have Tailscale rigged to use PiHole as the tailnet DNS to have adblocking on the go.
Guess that restart: always value in the Compose config is pulling it’s weight lol
I ended up on the snap because I couldn’t get the AIO install working properly. My snap version has been super solid. I think I’m gonna stick with it for a while.
selfhosted
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.