I am hosting more than 10 services currently but only Nextcloud sends me errors periodically and only Nextcloud is super extremely painfully slow. I quit this sh*t. No more troubleshooting and optimization.
There are mainly 4 services in Nextcloud I’m using:
Files: as simple server for upload and download binariesCalendar(with DAVx5): as sync server without web UINotes: simple note-takingNetwork folder: mounted on Linux dolphin
Could you recommend me the alternatives for these? All services are supposed to be exposed by HTTPS, so authentication like login is needed. And I’ve tried note-taking apps like Joplin or trillium but couldn’t like it.
Thanks in advance.
If you’re having issues with NextCloud being slow and having errors, it’s probably because the machine you are running it on is low on RAM and/or CPU.
I bring this up because what ever replacements you try would likely have the same issues.
My NextCloud instance was nearly unusable when I had it on a Raspberry PI 3, but when I moved it to a container on my faster machine (AMD Ryzen 7 4800U with 16GB of ram) it now works flawlessly.
I agree with this. It needs a good amount of CPU cycle and RAM. Raspi struggled for me too.
My NC instance runs on a 24GB RAM, 4 CPU Ampere A1 host(Oracle), and still struggles. YMMV.
And it struggles as a photo backup host an i5-7xxx and 16GB RAM at home.
It’s not absurdly slow, it’s just…irritating sometimes.
Whta db are you using
Postgres.
Also using redis, did all the typical perf checks listed on NC site etc.
Yeah, Ive got this in my setup as well and its been pretty slow. I thought it was a network thing because I’m currently using Tmobile home internet but switching to a fiber optic network with 500Mbps up and down soon. Im really hoping that changes things
There are performance tuning tweaks you can do on NextCloud like memory caching etc.
Ooo Lovely! I’ll look into that!
The backing database type and the storage it runs on are just as important too.
Experiencing the same, a good CPU and lots of RAM would resolve the issue
Even if you ran a basic sqlite nexcloud, if properly optimized, you can deal with millions of files like its nothing. And that is the issue, the bugs and lacking optimization…
4650g + 64GB ram + Mysql and it was file locking on just a 21k 10GB folder constantly.
I have written apps (in Go) that do similar and process data 100 times faster then nextcloud. Hell, my scrapers are faster then nextcloud in a local netwerk, and that is dealing with external data, over the internet.
Its BADLY designed software that puts the blame on the consumer to get bigger and better hardware, for what is essentially, early 2000 functionality.
Mysql and it was file locking on just a 21k 10GB folder constantly
It’ll definitely do that if you keep your database on a network share with spinning disks.
Spin up a container with sqlite in a ram disk and point it to your same data location. Most of the problems go away.
It’ll definitely do that if you keep your database on a network share with spinning disks.
Database and Nextcloud where on a 4TB NVME drive … in Mysql with plenty of cache/memory assigned to it. Not my first rodeo, …
I’m running on an SSD as a VM on 10yr old laptop and have had very few issues compared to running on Raspis in the last. It’s not my first rodeo either and found Debian with NexCloudPi setup script worked the best, then restore from backup. The WebUI is performing great as well as bookmarks, contacts, calendar, video chats and most things I’ve thrown at it. NVME may be overkill but the combination of solid CPU, RAM and Disk IO should alleviate any problems. My hunch is there are other resource constraints or bottlenecks at play, perhaps DDOS or other attacks (experienced that for sure and you can test by dropping your firewall ingress rules to confirm).
Also, this is FOSS and I find the features and usability are better than anything else out there, especially with Letsencrypt.
Same and looking forward to the responses here. Nextcloud is too big and complicated. I deployed Immich to cover for the photo library. Still looking for a good solution for notes though.
I have my issues with Nextcloud, but it’s still, by far, the best solution I’ve come across.
Sorry to hear you’ve had a bad experience. I’ve been running the lsio Nextcloud docker container for 4 years without any issues at all.
What exactly have you tried to do to address your nextCloud problems?
I was on the same boat when I was running NC on a container. I switched to VM, and most of my issues have been resolved, but collabora. I am currently using the built-in collabora server, which is slow.
- Syncthing for files.
- Proton calendar (so not self hosted)
- Joplin, using file based sync with aforementioned syncthing. I saw you didn’t like it though.
- I occasionally use scp
For calendaring, I also went with the option of syncthing via DecSync. I can get my contacts and calendar on Android and Thunderbird, so I can avoid yet another unnecessary webapp.
This does look cool! But I notice that there’s really only one contributor (technically two, but the second only did one tiny commit) and they haven’t contributed any code in over a year. I don’t want to invest too much time migrating to a stale if not dead project.
Honestly, I think that the lack of commits is more due to the application being feature complete than “dead”. I’ve been using it for at least 3 years now and it works quite well.
That’s a fine point! You talked me in to checking it out. Thanks for the recommendation!
Files: SYNCTHING CalcardDav: Baikal Notes: Obsidian with livesync plugin and a couchdb as backend …yeah and webdav for folder shares inside apples files app
Files: Seafile
Calendar: Radicale
Notes: Joplin
Network Folder: N/AI use pydio cells for file sharing.
I would say Seafile, and especially their webserver “seahub”, which is written in Python and Django, is just pure garbage. I’m using Seafile since 2012, and I’m honestly so sick of its problems. It just crashes for no good reason, and the encryption is extremely mediocre (there’s been issues about it). I have it behind my VPN so security isn’t a big deal.
Because it’s written with the garbage Python + Django, just try moving your installation to a new version… and you’ll be stuck with a very specific version of a bunch of libraries or otherwise seahub won’t even launch… and to make it even better, you don’t get anything on stdout/stderr to tell you what’s wrong, unless you launch Seahub in a specific configuration mode (WSAPI or something?).
Seafile has become so bad that I stopped caring about tracking its issues. I set my docker container to just restart on health checks’ failure, and forgot about it. My status tracker shows that it’s shutdown, and eventually it’ll restart. “Hey look, Seafile is down.” And I respond “That’s OK, dear, just give it another 15 minutes and it’ll restart”. This is my status on Seafile.
I think Seahub needs a complete revamp.
Those guys coded Seafile like a decade ago and they don’t care about fixing it anymore. Github is cluttered with issues.
i dont understand how some people have lots of issue with NC and some people say its all good
i have tried many times to switch to NC, It always slow (given that it running locally next to me, i expect it to be snappy) and throws me some error after somedays. I really wanted to use NC, so many things in one package
NC AIO has been good for me and support has been awesome. Seafuke is Chinese so I don’t trust it. At least NC is German and has some privacy stuff.
Filerun is good
Don’t get me wrong NextCloud is great and has a lot of helpful features out of the box, but I moved from this to just use;
- Samba: for mounting drives shares.
- CalDav: for shared calendars.
- CardDav: for shared contacts.
- Memos: for note taking, great little room that allows Markdown note with tagging for easy search and filter.
- Espo CRM: for logging communication with businesses, like utilities providers (comes in handy to refer to during disputes)
I’m also looking at installing a self-hosted office suite for word and Excel documents but haven’t set this up yet.
I love idea of Nextcloud, but its overall concept of doing everything, but nothing well enough was one of the reasons I’ve decided to build S3Drive. We squeeze most of the “file-management” experience out of the protocol itself. That means that all you need to self-host is the S3 storage server (e.g. MinIO)… but if you don’t feel like it just yet you can buy S3 from anyone else (e.g. Backblaze / Wasabi / Synology / Cloudflare etc.) and enable 100% Rclone compatible E2E encryption to protect your privacy.
