I tried Nextcloud a while back and was not impressed - I had issues withe the speed of the Windows sync that were determined to be “normal” with no roadmap to getting fixed. I’m now planning to move off Windows desktop so that won’t be an issue - so I thought I’d try again.
I went to nextcloud.com, clicked on Download-> Nextcloud server -> All-in-one -> Docker image - Setup AIO. This took me to the github README at Docker section. I’m already running docker for other things so I read the instructions, setup a new filesystem for my data directory and ran the suggested docker command with an appropriate “–env NEXTCLOUD_DATADIR=”. I’m then left with a terminal running docker in the foreground - not a great way to run a background server but ok, I’ve been around for a while and can figure out how to make it autostart in the background ongoing. So I move on to the next step - open my browser at the appropriate URL and I’m presented with a simple page asking me to “Log in using your Nextcloud AIO passphrase:”. I don’t have a Nextcloud AIO passphrase and nothing I’ve read so far has mentioned it. When I search for it I get some results on how to reset it, but not much help. I could probably figure that out too, but after reading some more I found that Nextcloud requires a public hostname and can’t work with a local name or IP address. I’m already running my home LAN with OpenVPN and access it from anywhere as “local” - I don’t really want to create a new path into my home network just for Nextcloud.
I’m sorry - I know this sounds like a disgruntled rant and I guess it is. I just want to check that I’m not missing obvious things before I give up again. All I want is a simple file sync setup like onedrive but without the microsoft.
And here I am having used it for a decade and perfectly happy. I try other ones like Owncloud every once in a while and find them lacking. It was slow once upon a time but if you changed to postgres and used redis, it improved immensely. Today it’s quite fast and the sync has been working great for a long time.
Use docker-compose with the AIO and it’ll be a lot easier to manage. There’s example compose files in the github repo.
I’m in the process of (very slowly) migrating my household from Windows to Linux and am currently testing Nextcloud as a replacement for OneDrive. In my case, I set it up using pikapods.com because I want offsite storage. The server part of the setup was incredibly easy because the host did all the work.
Getting my Linux client setup was kind of a pain (especially compared to the Android and Windows clients), but everything seems to work ok so far. Of course, I’m only backing up a small amount of data so far, so I can’t comment on the efficiency or speed for a major backup.
Alternatives? https://filebrowser.org/
There’s a lot of stuff going on here, so let me break down your post for each issue:
-
You need to understand the difference between a
docker run
command, and detaching to run a container in the background. Just running it with ‘run’ keeps it in the foreground. -
For the passphrase issue: https://github.com/nextcloud/all-in-one/discussions/1786
-
Lastly, if you’re not familiar with containers, and this is a single purpose machine, you’d be better off just running the bare project on the host. If there’s no need for containerization, just skip it.
You need to understand the difference between a docker run command, and detaching to run a container in the background. Just running it with ‘run’ keeps it in the foreground.
Yes, I understand this. I was just highlighting that it’s not a great experience for a new user to follow the instructions to setup a server and be left with it running in the foreground.
For the passphrase issue: https://github.com/nextcloud/all-in-one/discussions/1786
Thanks! This should get me past my current hurdle so I can do some more testing. Again - not a great experience to have to come to a forum to get help to find a passphrase. I’m pretty sure I didn’t miss any steps?
Lastly, if you’re not familiar with containers, and this is a single purpose machine, you’d be better off just running the bare project on the host. If there’s no need for containerization, just skip it.
I’m familiar with containers, but think they’re overused. Stupid little things that are a single Python script (for example) shipping as a Docker image! But, I thought Nextcloud was complex enough to be worthy of a container? This is not a single purpose machine, but I’m an old, retired, sysadmin - I have no problem running a few different servers on the same host.
Are you referring to the “Archive” Community Project installation method?
No, just clone the project and run it without a container. The docs cover that as well.
-
Nextcloud file sync is a convenient centralized solution but it’s not designed for performance. Nothing about Nextcloud is designed for performance. It’s an “everything and the kitchen sink” multi-user cloud solution. That is nice for a lot of reasons. Nextcloud Sync is essentially a drop-in replacement for Google Drive or OneDrive or Dropbox that multiple people can use and that’s awesome. It works the same way as those tools, which is a blessing and a curse.
Nextcloud is for the same role you SAY you want, “All I want is a simple file sync setup like onedrive but without the microsoft.” That’s what it is. But I don’t think it’s what you’re actually asking for, and it’s not supposed to be. It has its role, and it’s good at that role. But I don’t think you actually want what you say you want, because in the details you’re describing something totally different.
If you want performance sync for just files, SyncThing is made for this. It has better conflict resolution. It has better decentralized connectivity, it doesn’t need the public IP server. It uses a very different approach to configuration. Its configuration is front-loaded, it takes a fair bit of work to get things talking to each other. It’s not suitable for the same things Nextcloud Sync is. But once you have it set up it’s rock solid reliable and blazing fast.
Personally I use both SyncThing and NextCloud Sync. I use them for different purposes, in different situations. NextCloud Sync takes care of my Windows documents and pictures, I use it to share photos with my family. I use it to sync one of the factors for my password vault. It works fine for this.
I also use SyncThing for large data sets that require higher performance. I have almost 400 GB of shared program data, (and game data/saved games), some of which I sync with SyncThing to multiple workstations in different parts of the country. It can deal with complex simultaneous usage that sometimes causes conflicts. It supports fine tuning sync strategies and files to ignore using configuration dotfiles. It’s a great tool. I couldn’t live without it. But I use both. They both have their place.
I use both as well. They server different purposes. When my wife wants to take a quick scan of a paper document and archive it instantly, or have pictures auto-upload, or open and edit a document we worked on a year ago, all on her IPhone, the Nextcloud client works great and really has no competition in the iOS world. When I want to keep the files in my home directory, including some big, regularly changing files, instantly synced between computers and hosted VMs, Syncthing is amazing. I also add Syncthing shares as an external source in Nextcloud, so I can open those files via the web. As others have said, Nextcloud works fine, provided you don’t start installing all sorts of “apps” you don’t need -stick to the basics.
Honestly I hate all these file sharing self hosting things. Looking at you nextcloud owncloud syncthing seafile etc. They all suck. All I want is NFS support in android, that’s my only pain point accessing my files from anywhere from my home network. I can already VPN/wireguard into my network from anywhere, but I can’t grab an ebook or mp3s off my NFS server from my phone or tablet, I have to have some other dumb infrastructure for it. Just (#@$^* put NFS in android already!!!
/endrant
Yes! There used to be a little utility that could map a SMB share in Android, but that got killed years ago.
My biased opinion is that most people run Nextcloud on an underpowered platform, and/or they install and enable every possible addon. Many also skip some important configurations.
If you run NC on a bit more powerful machine, like a used USFF PC, with a good link to it, the experience is better than e.g. OneDrive.
Another thing is, people say “Nextcloud does too much”, but a default installation really doesn’t do much more than files. If you add every imaginable app, sure it slows down and gets buggy. Disable everything you don’t need, and the experience gets much better. You can disable even the built-in Photos app if you don’t need it.
Not saying NC is a speed daemon, but it really is OK. The desktop and mobile clients don’t get enough love, that’s true.
I’m talking about the “bare metal” installation or the community Apache/FPM container images. AIO seems to be a hot mess, and does just about everything a container shouldn’t be doing, but that’s just my opinion.
Agreed. You also have to make sure you get everything configured correctly. The admin should get some suggestions for set up needed in the settings screen.
I also had to provision a lot of cpu cores for it. It doesn’t use much while idle, but try to pull a doc or picture, and you’ll see the cpu usage skyrocket.
And at the end of the day, it’s going to be heavily impacted by your disk speed. If you want superior performance, time to consider data center grade solid state drives.
Your opinion is a hard-learned lesson here. I only recently figured that out. The Nextcloud “app store” is just too tempting.
Seafile. It’s super fast and lightweight. There are some caveats though:
-
Data is stored in git-like chunks on the server side. There is Seafuse and Sea drive functions that you can leverage to “assemble” the data on server side for backups. I personally use rclone mount, then backup.
-
Paywall hiding some features. The community edition is free but is missing some features that pro has. Pro edition is free for 3 or less users.
-
Documentation isn’t great. The forum is active so that’s helpful, but some of the docs take some time to understand
-
Chinese owned. As far as I can tell, there is no call home for a self hosted server, so I don’t think it’s a worry in that case.
All that said, I like it much better than Syncthing for it’s selective sync. All files on each client are synced to the server. But unlike Syncthing, it doesn’t sync all data with each client. This is vital for me with some devices with small storage drives, so I would t want all files to sync. Yet I can still reach to the server from any client and pull data from any other client. Syncthing has an ignore flag, but that seemed way more trouble to setup than just sticking with Seafile.
-
I’ve never used the AIO image. I’ve heard it’s weird. This is my compose file for the community image:
compose.yaml
volumes: db: services: db: image: mariadb:10.6 restart: always command: --transaction-isolation=READ-COMMITTED --log-bin=binlog --binlog-format=ROW volumes: - db:/var/lib/mysql secrets: - mysql_root_password - mysql_nextcloud_password environment: - MYSQL_ROOT_PASSWORD_FILE=/run/secrets/mysql_root_password - MYSQL_PASSWORD_FILE=/run/secrets/mysql_nextcloud_password - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud nextcloud: image: nextcloud restart: always ports: - 8080:80 depends_on: - db links: - db volumes: - /var/www/html:/var/www/html - /srv/data:/srv/data secrets: - mysql_nextcloud_password environment: - MYSQL_PASSWORD_FILE=/run/secrets/mysql_nextcloud_password - MYSQL_DATABASE=nextcloud - MYSQL_USER=nextcloud - MYSQL_HOST=db secrets: mysql_root_password: file: ./secrets/mysql_root_password.txt mysql_nextcloud_password: file: ./secrets/mysql_nextcloud_password.txt
You can access it on port 8080 and perform the initial setup manually. For the database server address, use the
db
hostname. You’ll have to use a reverse proxy for HTTPS.You could also try OpenCloud, which is a Go rewrite of ownCloud.
I’ve never used the AIO image. I’ve heard it’s weird.
It does seem to be. So, I find it weird that the “core” documentation leads a new user to installing AIO.
You could also try OpenCloud, which is a Go rewrite of ownCloud.
Sounds interesting - thanks.
So, use something else, like Seafile.
So, use something else
That’s why I’m here - looking for suggestions
like Seafile.
I’ll have another look - you’re not the only person to suggest it. My recollection is that it seemed to be old and not really maintained.
Yeah setting it up the way you want is a pain, but I like it mainly for backing up photos from my phone automatically, as well as, syncing podcasts and music between devices since I moved away from Spotify and start using things like AntennaPod and Gramophone
I got 20TB in my server, might as well use it.
Oh wait, were you looking for alternatives? I guess this also works: https://filebrowser.org/
Its just web veiw to file server instead of only using things like smb or nfs
There are a number of ways to install nextcloud, and docker is only one of those.
Yes, NC isn’t ideal in many ways, but it shouldn’t be as painful as you’re describing to run it.
I just use SMB shares on my NAS. Why over think it?
Because an android client is one of my requirements. I can get files from SMB on Android using any number of file managers, but I can’t map a SMB share to a filesystem so files are available for an app to use.
If you only need onedrive replacement. You might want to try seafile.
I like nextcloud tbh even it tries to do everything and not being really good at it. When i set it up the first time. I scoured the internet like you wouldnt believe. Took me couple of days optimizing it.
Now, it runs okay. Has been a few months since it set it up. No complain except a couple of weeks ago android app wont auto upload for some reason, had to logout and login back.
My main use is cloud storage, photos, note, task, contacts and calendar. Works fine on my android, linux and my wife’s iphone.
I didn’t know anything about docker when I set up my NC years ago, so I ran it as a snap on bare metal. Man, it’s gotten so much better! It used to really suck. Like, simple file transfers just didn’t work half the time, so I’d be retrying the same thing over and over… A few years ago, I literally migrated it from bare metal to a VM, but kept the exact same install. I have so much crap on it now, I think I’ll never bother switching it out to docker, just because of the inconvenience. I know the snap version can just run using a local hostname, you just have to set it in trusted domains setting. Might be the same in the docker image?