We selfhost Nextcloud on our local Unraid server with a backup Nextcloud instance on the old Unraid server plugged in at my parents’ house. Second redundancy is an rsync job to a pCloud account.
Next cloud as front end with external storages mounted over sftp.
Main storage is distributed on multiple Raspberry Pips and SSDs I got at home. Really not too smart/smooth/fast, but it gets the job done.
I see NextCloud here quite a bit. What I don’t see discussed is the cloud hosting option.
Hetzner has two NextCloud offerings.
They have a storage service backed by NextCloud. I think that’s new. I don’t use that.They also have have NextCloud available as an installable app from their service.
This is what I use. https://docs.hetzner.com/cloud/apps/list/nextcloud/
I had to actually follow the directions to get it running.
And I have to patch it occasionally. Mostly, it takes care of itself.I use the cheapest 1vcpu VPC.
Yes my NextCloud service is a bit sluggish sometimes. But I’m paying like $6/month.
I’m pretty happy with it for storing music and updating my resume.
Maybe if I had the more demanding use cases like some commenters, I might not like it so much.I used to selfhost Nexcloud in OVH (or rather Owncloud back then) but I tire of the update cycle and now I’m just paying for Hetzner for their Storage Box or whatever their Nextcloud product is called. I love selfhosting and don’t mind doing it at work but for some reason Nextcloud was annoying enough for me to switch paying to someone else to update it.
I think because I got into NextCloud to “de-google”, I just accepted some maintenance load.
My intent was to manage my documents. The CORE office suite works sufficiently. Now I update my resume (and manage a few other documents) on my own website, no google.
I uploaded a bunch of music. The music apps are kinda crappy, but they also work sufficiently.
I never got around to setting up email for NextCloud. Looks like maybe I never will.
My searxng instance in my homelab died, and I nuked it. I think when I rebuild, its going on this VPC.
I mostly just use the Synology files app or samba over wireguard, and then sync a couple tb of super critical stuff to rsync.net. I have next cloud set up but all I use it for is editing my cook book from multiple devices and storing the few documents I migrated off of gdrive, but I might as well just have them in a regular folder on my nas instead.
i don’t. i host some svcs like grimmory and plex but frankly if i lose my docs or pics whatever. after my wife died in 2011, I just havent cared too much. Like I have a good enough memory and physical pics.
/shrug
Wanted to setup opencloud but it doesn’t work without 3-4 additional containers and CNAMEs on the domain.
I simply wanted to spin it up locally and test it out, but it doesn’t accept any admin credentials whatsoever and wiping every file to completely restart leads to the same behavior.
If the simplest bit of startup flow local first time login doesn’t work, then why would the rest and why would I trust it? Also it isn’t a certificate error with not setting up SSL or something because I also tried it on my domain with all the correct certificates and got the exact same behavior. It doesn’t even allow you to try a different admin password when it claims that the last is wrong. You get one try and otherwise have to wipe the entire volume.
There are issues on github for it and workarounds with very YMMV results, for me none of it worked.
Seafile, gets the job done, is lighter on resources than Nextcloud and all its cool features, and encrypts everything so my friends can store stuff on the server with peace of mind. I also use Immich for photo backup. And am in the process of setting up Duplicati with a friend’s server. (Unraid)
idk why, I really wanted this to work but could not, for the love of me, get Seafile working properly with my setup 😬
Wild, for me it was basically as simple as picking the unraid setup and pressing go - way less difficult than my first experience with Nextcloud (which was back before the All In One).
I use rclone to mount via webdav. Works like a charm 👌
SFTP
Zfs, nfs, ssh, wireguard.
Nextcloud. It does the job well enough.
It took about 2 days of using nextcloud files across devices to experience unreliable syncing from Nextcloud on Android.
I installed folder sync pro on android and that has helped a lot, but it still irks me to use 2 tools when 1 should do the job.
Did you try Syncthing at all? I ran into the same issues with Nextcloud on Android and I’m trying to decide on Syncthing or FolderSync and I wanted to see what people thought. I’m currently using Cryptomator but it doesn’t do everything I’d like yet.
People love syncthing but I spent about 20-30 min on setup and found it confusing once I got beyond 2 devices. There are a couple comments in this thread between me and someone else about different setup options with syncthing.
I have been relatively happy with folder sync pro and nextcloud though. It’s worth noting that changes only instantly push when they’re made on Android first. If you edit/add/remove a file that’s in a synced folder from a computer, then folder sync pro on Android will simply use the sync interval that you set (I have mine at 15 min and have seen no battery hit, can set it down to 5 min). You can also just manually hit the sync button in FSP. But that was just one element that I was troubleshooting and thought sync was broken, but nope, that’s just how it works depending on what device did the edit/add/remove.
Thank you! I did just find in the FolderSync docs that 2-way sync isn’t supported for encrypted files, which is a bit of a bummer. I think Nextcloud on Android had a similar limitation where it would only actually sync at most every 15 minutes. I did find the Cryptomator app on Android does have an “immediate upload” folder, but it’s only for images captured with the camera and screenshots… which I guess for now fulfills most of my needs, so I may stick with that after all.
opencloud, i just moved from nextcloud and wow, the performance is insane.
Wanted to use open cloud but they archived their helm chart. Very niche I know, but still a shame
I set up Nextcloud with RPi4 based RAID NAS. Via sftp as apparently it is not really that much slower and NFS felt weird to me
I bet my answer is going to be the least interesting one but let’s represent casuals too ;)
Keep it simple, stupid my friend :D
Well, now I see that I’m going to move to have sshfs instead. There are issues with spamming sftp connections for all the small files. But in general I’ve learned that really “done is better than perfect”. Just make it work, observe, iterate
@pixeldaemon Syncthing. We have one “authoritative” fileserver running syncthing, and then a bunch of “clients” (laptops, phones) that sync up to the fileserver. This doesn’t work for, say, terabytes of movies/music, but for important stuff like photos/tax records/whatever, it means we can make changes on any “client” and it gets synced to the “server” and all the other “clients”
For more traditional cloud, I recently installed copyparty (https://github.com/9001/copyparty) w/ https://github.com/romaan7/white-gold-theme-for-copyparty
How do you set up syncthing with a host/client configuration?
I planned on setting it up with 5 devices but as soon as I got to 3 devices I started having issues and didn’t like the structure conceptually of “everything syncs to each other” vs having a “source of truth” with 2-way sync.
TBF my issues with syncthing were probably user error but still frustrated me enough that I bailed.
@yestalgia So I set up syncthing between a server and one client. Share folders between them. Figure out how you want the folder data replicated; for my phone pics, for example, the sync is one way from (phone) -> (syncthing server). For kids’ health stuff, it’s a two-way sync; because the sync might be (my laptop) <- (syncthing server) <- (my wife’s laptop), or vice-versa. Then add another client to the syncthing server, following the same process. Never sync client-to-client; always via server
@yestalgia I will say that the configuration is not the most intuitive. Part of it is just that the web UI is, imo, not that good. There’s a lot of confusing stuff exposed to users that isn’t really important for like 99% of use cases.
(who cares whether compression is metadata only or all data or none? wtf is “introducer” vs “auto-accept”? why do I need to see a random hash for device or folder id in addition to a device or folder name?)
@pixeldaemon I used to use Seafile, but it is clunky and annoying, and it will also never ever be in debian due to upstream copyright sketchiness.
