Additional instructions for setting up AIO

ℹ️ Support
1

I know about the AIO installation document found here:
https://nextcloud.com/blog/how-to-install-the-nextcloud-all-in-one-on-linux/

Apparently this is only the beginning to get NextCloud installed in docker. Is there a document that covers the myriad of other things I’m supposed to do to get NextCloud AIO?

I ask, because apparently there’s some other steps so that it actually stays up to date. Please don’t just say read the manual, I have, and it’s 150 pages that aren’t separated by topic or by what steps are important and what are there in case of trouble.

1 Like
2

Actually, I am not familiar with that blog post. I would rely only on this link for installing and configuring nextcloud AIO. This is the official install doc. There’s alot in there, so be prepared to spend alot of time perusing it! :slight_smile:

1 Like
3

With the Docker Run Command from the blog post, you get a complete AIO, and you can then install/uninstall individual components such as Office, Fulltext Search, Whiteboard etc. via the AIO web interface, and you can also manage updates and backups via this.

Well the manual (I assume you are talking about the manual @TobiasEigen linked to) includes all kinds of scenarios and usecases that may or may not apply to you.

At the end of the day, it depends on what kind of infrastructure you are running AIO on. To keep things simple, I would recommend installing it on a dedicated server or in a dedicated VM, or if you want to host it in the cloud, on a dedicated VPS, where you can expose all ports needed directly to the internet.

Things start to get complicated if you want to integrate it into existing environments, like existing Docker stacks, or if you want to install it on NAS systems like Unraid, Synology, TrueNAS etc, or if you want to access it in airgapped environments via VPN and/or on an internet connection behind CG-NAT and then overlay networks like TailScale or Cloudflare tunnels come into play, or all of the above combined :wink:

3 Likes
4

Just FYI: there is a good overview about most options available here: all-in-one/compose.yaml at main · nextcloud/all-in-one · GitHub

2 Likes
5

Awesome! That compose.yaml file is super helpful and I keep forgetting about it. It’s linked to from https://github.com/nextcloud/all-in-one fairly prominently so anyone relying on that should be good. I will add it to my own notes. (@SamanthaSass keeping notes of what you’ve done and learned so far is also highly recommended!)

Is the blog post kept up to date? It’s well written but I don’t see any date on the page indicating when it was written and last updated. That’s why I’d recommend relying only on the official instructions.

At Discourse, we have a similar blog post announcing the easy, official install but then we link to the official installation instructions. This has worked well for us over the years because we only have to keep the official installation instructions up to date!

1 Like
6

Yes, it is

1 Like
7

I’m going to go with NO, it’s not fully up to date. Two glaring points are missing which is what prompted this topic.

  1. Nothing in that post mentions setting up backups after getting it installed.
  2. Nothing is mentioned about setting up the update system.

I mention this because this is I believe the 4th time I’m installing NextCloud. The installation documents never seem to be complete, and the update system doesn’t work unless you run it daily. (perhaps weekly)

Also before you try to tell me I’m wrong, The manual update that you’re so fond of pointing people to is why I have to start over again. It doesn’t work.

NOTE: all-in-one/manual-upgrade.md at main · nextcloud/all-in-one · GitHub will not update major version from v27.x after following this method, restarting the containers will break AIO. Specifically Method 1 #8. …sudo docker restart nextcloud-aio-nextcloud doesn’t update the container.

1 Like
8

I see. Yes, you are right. This is because it is only the installation instructions. By default it will in that state send update notifications regularly like this: GitHub - nextcloud/all-in-one: 📦 The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.

However setting up backups and daily backups as well as automatic updates is fairly easy. See for example this video timestamp: https://youtu.be/U47nvwXrAOo?t=1290

1 Like
9

Notes for anyone else who runs into these issues

So it is reinstalled, and I managed to get the accounts built and synced. The issue I’m seeing now though is every time I try to log in, I get “too many requests” and have an impossible time trying to log in as the administrator. There isn’t even that many accounts, and I’ve never had this issue previously.

I did find this: Cannot login: Too Many Requests - #16 by Da01W6hwz but it doesn’t seem to work. I was able to get in by restarting the nexcloud-aio-nextcloud container yesterday, but today it’s doing the same thing again.

For clarity, I’m running this command

sudo docker exec --user www-data -it nextcloud-aio-nextcloud php occ security:bruteforce:reset 192.168.0.9

The IP address is the server that is hosting docker. it has a GUI and I’m attempting to connect using Firefox using the FQDN. This doesn’t fix the issue. Apparently it’s the external IP that is causing the issue.

I did eventually find this: https://www.youtube.com/watch?v=UTVu0Psfaao which seems to have temporarily fixed the issue.

I was able to get in and whitelist the appropriate IPs, so I should be good on that front. Now in a cruel twist of fate, the mastercontainer has now stopped. Turns out there is now a conflict on port 8080. wasn’t an issue in the past which is why I was using it for apache2. Moved that to another port, and it appears to be working.

After discussing these issues with someone else I was informed about this: Notification: Changes to our Nextcloud image | Info :: LinuxServer.io It appears to be a single docker install that solves the issues surrounding AIO.

Finally:
Install AIO and follow the setups as instructed on a docker system with nothing else running. There are way too many chances for conflict.
If you have to restore from backup, go look up those instructions before doing anything, Actually installing docker and restoring a backup are not compatible.
After installing, set up the backup and check the box to update.
The update system is not reliable on any system that hasn’t been updated for more than 3 months.
If NextCloud breaks, repair is temporary, and plan for reinstall.

While I realize I will be blamed for all the errors, I will also say that the documentation could be vastly improved.