I have been using Nextcloud for a little over 6 months now. I love it. I have been using it for myself since last September and I just deployed it for a client of mine as well. In both cases I used the VM resources, although in the client’s case I actually used the VM script from HERE to deploy it on a fresh install of Ubuntu Server 20.04.2 running on an old machine that would otherwise have been retired. It was one of those things that no one said would work that I figured would work, and it did. However, I wouldn’t recommend doing the installation on a physical server this way unless you are planning to dedicate the device to NC, but we were, so it was perfect. For my own, I am using the prebuilt VM on a Windows host. I started with the NC19 VM, then recently migrated my data to a fresh NC21 VM, which was a nice upgrade. (I dumped the data out of the old one to a Windows share via CIFS, then imported it into the new one the same way.)
That is all background information. The issues I have are only annoying, and nothing that interferes with usability, but I would like to understand why they are happening and resolve them. 2 of them I believe are connected.
Connecting insecurely gives the landing page with “Thank you for downloading the Nextcloud VM, you made a good choice! If you see this page, you have run the first setup, and you are now ready to start using Nextcloud on your new server. Congratulations! :)” I would have thought that this would only appear once and then it would simply forward to the secure login page.
Running “sudo -i” to gain root, sometimes because I really need it and sometimes because, yes, I’m too lazy to type sudo repeatedly, triggers the first run script every time I do it. Of course it quits quickly because it realizes it has already been run, but it would be really nice to have “sudo -i” just give me root rather than griefing me with the script every time.
On the most recent deployment, on the physical machine, I attempted to run the automatic backup wizard from menu.sh but it gave me the same error it did when I tried to run it from the setup script, that it can’t be run during the initial setup.
Clearly some things are not getting properly cleared away after the initial setup, and I’d like to know what they are and how to clear them. I could probably dig around for many hours and figure out what they are, but if someone knows and could spare 5 minutes to tell me, I’d be very grateful.
T&M Hansson IT AB are rockstars. The amount of energy they have put into this product and made available to the public free of charge is astonishing. “Pro bono” doesn’t mean “for free,” though that’s how it’s generally used; it means “for good,” or as a contribution to the greater good. These guys have done so much pro bono work that it is a little shocking. Thank you so much!