8 ms·

I really wish there was an LTS release that was supported for at least 2 years (just bugfixes, no new features). I self host my own instance, and I really just

by l72 6y ago

I really wish there was an LTS release that was supported for at least 2 years (just bugfixes, no new features). I self host my own instance, and I really just want to set it and forget it. I don't mind doing low risk patches every few months or weeks, but I don't want to do a major version upgrade every 4-6 months. I did my last major version upgrade only 15 months ago, and I am now 4 major versions behind, which means: 1) I upgrade from 17->18->19->20->21 and hope nothing breaks! 2) I either start over with the latest version I like that open source moves fast, but at some point, I just want to stop fiddling with it and let it run with minimal maintenance.

znpy 6y ago
> 1) I upgrade from 17->18->19->20->21 and hope nothing breaks! I did a similar path (started from 18 iirc) and nothing broke. But there's a catch, because I have some safeguards in place: 1. Nextcloud has its own dataset in a ZFS zpool. I take snapshots hourly, and I took a snapshot just before upgrading 2. I run nextcloud and its own postgreql via docker-compose. the docker-compose file along with the configuration and data are stored in nextcloud's own dataset. This means that os-level dependencies are not a problem for me. this also mean that reverting the whole thing to before-upgrade is very easy: just rollback to the before-update snapshot. 3. (unrelated) snapshot are replicated to another location, which means that I might perform the upgrade on that other site and switch the dns when it's done and if i'm satisfied. I don't do that, for my personal use 1-2 hours downtime it's okay. 4. I'll let nextcloud perform its auto-upgrade procedures, take a snapshot after every upgrade, and at the end I'll perform the tasks suggested in the self-assesment page (adding indexes, changing columns types etc). You don't have a nextcloud problem, you have a system administration problem.
- prophesi 6y ago
  > You don't have a nextcloud problem, you have a system administration problem. Those aren't mutually exclusive. Sure, better dev ops would make major upgrades safer and easier. But for a hobbyist self-hosting their own instance, a LTS release would be a godsend to save them hours of unpaid work.
  - znpy 6y ago
    An good hobbyist should challenge themselves from time to time ;)
    - zelon88 6y ago
      We wouldn't tell Google engineers to mess with his Google drive in prod... why should he sacrifice data availability and integrity?
    - nickthemagicman 6y ago
      Maybe they're challenging themselves on things that interest them more...and just want a functioning Nextcloud instance?
    - imwillofficial 6y ago
      Who said it was a challenge? When does grunt work move beyond challenge to the point of not being worth it? I got out of self hosting because my time is too valuable. It did teach me lots of new skills, so that was great! However, somebody not wanting a time sink, is not them avoiding challenge.
      - prophesi 6y ago
        This is the boat I'm in. And even if you do "everything right" and have snapshots before & after every update, you still need to actually debug why the update failed in the first place. So even then, LTS releases would be a greatly appreciated feature.
- contravariant 6y ago
  I don't disagree but as a hobbyist I don't really want system administration problems. Well and I was mostly interested in Nextcloud as a possible alternative to Dropbox/Google drive with versioning and, I hoped, backups. However the only proper backup solution that I could confidently state would allow me to recover should disaster strike was the one you just explained e.g. putting everything in docker and snapshotting the entire filesystem. At which point I'm basically running 3 virtual file systems on top of each other just to have a better UI, which seemed a bit silly.
  - znpy 6y ago
    First things first: don't get me wrong, I do understand your point. The thing is: you have a system administration problem, whether you want or not (that is a big part of what you're actually paying for when you buy Dropbox or when you let Google feed on your data). Now, as an hobbyist, when you start depending on services you set up and manage yourself, it would be a good idea to take some time to learn additional tools to enjoy your hobbies more. Think about this as in "leveling up" your hobby. --------------------------------------------------------------------- Now on a lighter tone, there are simpler ways to have a backup strategy, as long as you are okay with lower guarantees. You might not use zfs, and use simple LVM snapshots. You might want to use no snapshotting at all and just do a nightly backup via a cronjob: at 3AM you just switch everything down (docker-compose down if you're using it), do a rsync to another host, start it back up. It's way simpler but you'd only get a yesterday's copy in case of problem. But then again, that would safeguard you when doing upgrades: disable backup, perform upgrade, test everything, re-enable backup, resume operations. Worst case scenario you rsync back the yesterday's data and you resume normal operation.
    - dsr_ 6y ago
      > you have a system administration problem, whether you want or not Right. You can pay people to do things for you, or you can do them yourself, but either way the things have to be done, and they should be done by someone who is good at it and has a contract with you -- employment or otherwise.
- l72 6y ago
  That's very true. I run quite a few services on my local network for my family (wireguard, nextcloud, homeassistant, frigate, pihole, jellyfin, bitwarden, ...). While I enjoy setting up and playing with these service, I need to think about managing all these services as little as possible as I don't want to spend all my free time being a system admin. Also, often a new release is not just a system admin task. Sure, it may not be _that_ hard to do a full backup, pull new docker images, spin them up and verify everything. The time sink comes from keeping track of all the releases of all the different projects, reading up about changes, how the upgrade process works, and so on. On top of that, my family has become reliant on several of these services, especially nextcloud and bitwarden. The last thing they want are major changes to it. Long term stability with minimal changes can be a feature!
  - BrandoElFollito 6y ago
    I am exactly in the same situation as you (I did not know frigate, but I do not have cameras either - otherwise you listed my main systems). I managed to reduce administration to a minimum by using watchtower to automatically upgrade my containers and using mostly the :latest label. This bit me only twice in a few years: - with the 19-20 migration of Nextcloud, I had one big blank screen when logging in but the synchronization was working. Turns out it was a new default app (something about dashboarding) that was causing it. Googling an fixing took an hour. - with one upgrade of Home Assistant where my devices were not available anymore, there was a problem with the upgrade which they fixed quickly but I have already upgraded. Reading the docs/forum and fixing took an hour. I can live with these two hours across two or three years. I backup /etc on my server with Borg and I know that, worst case, I will recover. I tested this DRP two weeks ago bare metal (recovering to an empty VM from scratch, that is an ubuntu ISO and ultimately getting my encrypted backups from a friend's system -> it really helped to highlight what I was missing)
    - tp3 6y ago
      I'm currently testing a new appliance setup with Nextcloud which includes the ability to use containers as a default for everything, if your container can be moved to an empty VM, nothing gets deleted as I didn't touch it. I would be really happy if this helped.
- jcastro 6y ago
  > the docker-compose file along with the configuration and data are stored in nextcloud's own dataset. What a great idea!
basilgohar 6y ago
As someone who hosted his own as well, I agree with your sentiment exactly. I've taken down the server that I had hosting my own instance before this, and I am delaying setting up a new one simply because of what you've said here. I imagine that those of us that want that kind of stability are encouraged to go with their hosted offering, but hopefully they'll see the value in having a slower and/or more stable release process. For what it's worth, the upgrade process for the last few major versions went mostly without a hitch for me. I do have to give them credit for that. The only thing I continue to struggle with is the encryption design. I always end-up with some odd state for some files I cannot recover from.
- znpy 6y ago
  see my sibling comment for an idea on how to set nextcloud up for easy maintenance. disclaimer: i have updated several version, but haven't upgraded to version 21 yet (it just got released)
nmg 6y ago
I am a huge fan of Nextcloud and I couldn't agree more. My upgrade path is to just start a new instance with a fresh sync, because I was traumatized by a turbulent and uncertain upgrade on all of my instances once about two years ago. This is a product I love and choose to rely upon for my data, every day. I'm interested in the bells and whistles and I want the platform to succeed - my preference would be an LTS for my critical data, and the option to spin up newer features separately to test before adoption.
FredFS456 6y ago
In my experience of running my own Nextcloud instance for over 4 years, I've never had an upgrade break my instance. Caveat: I'm on the stable channel and I only update when the client prompts me to update, which is a few point releases into a new release.
- kop316 6y ago
  That's been my experience as well. I have run Owncloud -> Nextcloud (when it was first released) since at least mid-2015, and I am on the same instance I first built. I stay on the stable channel, and I get a notification if an app or nextcloud itself has an upgrade. The biggest issue is that the "Security & setup warnings" sometimes tells me I need to upgrade my database (and gives me the exact commands to do it) after an upgrade. I will note that the upgrade has taken longer over the years (it used to take 5 minutes, now it can take over 30 minutes), and I think there is an issue with the backing up stage.
  - znpy 6y ago
    > I will note that the upgrade has taken longer over the years (it used to take 5 minutes, now it can take over 30 minutes) In their defense, the software has grown a lot and does a lot more things nowadays, it's understandable that the upgrade process takes more.
    - kop316 6y ago
      Yeah, I was assuming it was either that, but I do notice that "backup" takes a long time. As soon as backup is done it is on the order of 4-5 minutes. But then again, I store something like 5 TB worth of files on my Nextcloud, so it could be me as well to.
      - znpy 6y ago
        > I store something like 5 TB worth of files on my Nextcloud Ah, that might be it. IIRC there's a database entry for each file, if you've got a lot of files it might take a while since on upgrade it also run database migrations to adapt to the new schema, that might take a while.
m463 6y ago
I agree - I wish it was more stable and a little less promiscuous. Having your instance have to access the cloud for apps and updates is sort of counter to the "control your own server" sort of mentality. Sort of like docker - do you have to go through their root namespace for everything?
regularfry 6y ago
The answer to that ought to be `apt-get install nextcloud-server` and let the distro maintainers step in, really. Unfortunately because you can't skip versions on upgrade, it's not clear how to cleanly do that.
- imwillofficial 6y ago
  That’s handled by the package manager.
  - regularfry 6y ago
    The package manager would need to have access to the code of all the intermediate versions to run the upgrades safely. That might work for some situations, but it's a hell of an overhead in general.
remram 6y ago
They also raise PHP version requirements. To keep my NextCloud on supported version, I had to update the Linux distribution on my server (was not EOL or anything) to get a PHP that supported versions of NextCloud support... I just wanted to keep getting bug/security fixes for NextCloud.
- gog 6y ago
  If you are running Debian or Ubuntu use https://deb.sury.org/ https://deb.sury.org/ for PHP.
tcit 6y ago
They can offer that with a subscription.
40four 6y ago
This has spawned a huge thread that I honestly didn't read all of, but someone else mentioned to me they use the 'Community' Snap package. I did not set mine up with this, but it apparently requires a lot less hands on maintenance. In your case you might be interested. https://docs.nextcloud.com/server/21/admin_manual/installation/source_installation.html#installation-on-linux https://docs.nextcloud.com/server/21/admin_manual/installati... https://snapcraft.io/nextcloud https://snapcraft.io/nextcloud Apparently it auto-updates for you, but I'm not sure if it will upgrade major versions, or only security patches.
- Forbo 6y ago
  The snap does upgrade major versions, although from my experience it tends to be on a delay to ensure stability.
  - 40four 6y ago
    Makes sense. Maintenance of self hosted services can be quite annoying, but I guess that’s the price we pay for taking control from the overlords :)
agilob 6y ago
Haha thanks to your comment I noticed I'm using nextCloud 16. I'm going to make a few upgrades now and I'll tell you how it went. Edit: Miration 18->19 is now stuck on Step 4 is currently in process. Please reload this page later. which is downloading zip with new version... Edit2: I restarted installation multiple times, increased pfp-fpm and nginx timeout to 660 seconds and still getting this error. Not today...
- cyphar 6y ago
  The issues with timeouts can be avoided if you use the command line upgrader: % php /var/www/nextcloud/updater/updater.phar
  - agilob 6y ago
    Yea, it didn't work as expected sudo -u nginx php updater/updater.phar Nextcloud Updater - version: v18.0.9-8-g27dac77 Current version is 18.0.14. PHP Fatal error: Uncaught Error: Call to undefined function NC\Updater\curl_init() in phar:///home/owncloud/updater/updater.phar/lib/Updater.php:455 Stack trace: #0 phar:///home/owncloud/updater/updater.phar/lib/Updater.php(119): NC\Updater\Updater->getUpdateServerResponse() #1 phar:///home/owncloud/updater/updater.phar/lib/UpdateCommand.php(147): NC\Updater\Updater->checkForUpdate() #2 phar:///home/owncloud/updater/updater.phar/vendor/symfony/console/Command/Command.php(256): NC\Updater\UpdateCommand->execute() #3 phar:///home/owncloud/updater/updater.phar/vendor/symfony/console/Application.php(820): Symfony\Component\Console\Command\Command->run() #4 phar:///home/owncloud/updater/updater.phar/vendor/symfony/console/Application.php(187): Symfony\Component\Console\Application->doRunCommand() #5 phar:///home/owncloud/updater/updater.phar/vendor/symfony/console/Application.php(118): Symfony\Component\Console\Application->doRun() #6 phar:///home/owncloud/updater/updater.phar/updater.php(10): Symfony\Component\Console\Application->run() #7 /home/owncloud/updater/updater.phar(10): require('...') #8 {main} thrown in phar:///home/owncloud/updater/updater.phar/lib/Updater.php on line 455
    - cyphar 6y ago
      You're missing php-curl (or it's installed but the module is disabled). I'd double-check that you have all of the dependencies of NextCloud installed[1], because php-curl is one of the required dependencies. [1]: https://docs.nextcloud.com/server/21/admin_manual/installation/source_installation.html https://docs.nextcloud.com/server/21/admin_manual/installati...
nucleardog 6y ago
> 1) I upgrade from 17->18->19->20->21 and hope nothing breaks! I've done this since about version 11. And I usually only get around to upgrading every few versions so it's been like... 11->12->13->14, 14->15->16, 16->17->18->19. I do each upgrade one by one. Upgrade, login, check system status and resolve any additional steps it suggests (e.g., adding indices/columns, etc) then jump right into the next upgrade. I've never had one fail on me. Even doing 3-4 major versions at a time it's usually less than a half hour problem.

by l72 6y ago

znpy 6y ago

> 1) I upgrade from 17->18->19->20->21 and hope nothing breaks! I did a similar path (started from 18 iirc) and nothing broke. But there's a catch, because I have some safeguards in place: 1. Nextcloud has its own dataset in a ZFS zpool. I take snapshots hourly, and I took a snapshot just before upgrading 2. I run nextcloud and its own postgreql via docker-compose. the docker-compose file along with the configuration and data are stored in nextcloud's own dataset. This means that os-level dependencies are not a problem for me. this also mean that reverting the whole thing to before-upgrade is very easy: just rollback to the before-update snapshot. 3. (unrelated) snapshot are replicated to another location, which means that I might perform the upgrade on that other site and switch the dns when it's done and if i'm satisfied. I don't do that, for my personal use 1-2 hours downtime it's okay. 4. I'll let nextcloud perform its auto-upgrade procedures, take a snapshot after every upgrade, and at the end I'll perform the tasks suggested in the self-assesment page (adding indexes, changing columns types etc). You don't have a nextcloud problem, you have a system administration problem.

prophesi 6y ago
> You don't have a nextcloud problem, you have a system administration problem. Those aren't mutually exclusive. Sure, better dev ops would make major upgrades safer and easier. But for a hobbyist self-hosting their own instance, a LTS release would be a godsend to save them hours of unpaid work.
- znpy 6y ago
  An good hobbyist should challenge themselves from time to time ;)
  - zelon88 6y ago
    We wouldn't tell Google engineers to mess with his Google drive in prod... why should he sacrifice data availability and integrity?
  - nickthemagicman 6y ago
    Maybe they're challenging themselves on things that interest them more...and just want a functioning Nextcloud instance?
  - imwillofficial 6y ago
    Who said it was a challenge? When does grunt work move beyond challenge to the point of not being worth it? I got out of self hosting because my time is too valuable. It did teach me lots of new skills, so that was great! However, somebody not wanting a time sink, is not them avoiding challenge.
    - prophesi 6y ago
      This is the boat I'm in. And even if you do "everything right" and have snapshots before & after every update, you still need to actually debug why the update failed in the first place. So even then, LTS releases would be a greatly appreciated feature.
contravariant 6y ago
I don't disagree but as a hobbyist I don't really want system administration problems. Well and I was mostly interested in Nextcloud as a possible alternative to Dropbox/Google drive with versioning and, I hoped, backups. However the only proper backup solution that I could confidently state would allow me to recover should disaster strike was the one you just explained e.g. putting everything in docker and snapshotting the entire filesystem. At which point I'm basically running 3 virtual file systems on top of each other just to have a better UI, which seemed a bit silly.
- znpy 6y ago
  First things first: don't get me wrong, I do understand your point. The thing is: you have a system administration problem, whether you want or not (that is a big part of what you're actually paying for when you buy Dropbox or when you let Google feed on your data). Now, as an hobbyist, when you start depending on services you set up and manage yourself, it would be a good idea to take some time to learn additional tools to enjoy your hobbies more. Think about this as in "leveling up" your hobby. --------------------------------------------------------------------- Now on a lighter tone, there are simpler ways to have a backup strategy, as long as you are okay with lower guarantees. You might not use zfs, and use simple LVM snapshots. You might want to use no snapshotting at all and just do a nightly backup via a cronjob: at 3AM you just switch everything down (docker-compose down if you're using it), do a rsync to another host, start it back up. It's way simpler but you'd only get a yesterday's copy in case of problem. But then again, that would safeguard you when doing upgrades: disable backup, perform upgrade, test everything, re-enable backup, resume operations. Worst case scenario you rsync back the yesterday's data and you resume normal operation.
  - dsr_ 6y ago
    > you have a system administration problem, whether you want or not Right. You can pay people to do things for you, or you can do them yourself, but either way the things have to be done, and they should be done by someone who is good at it and has a contract with you -- employment or otherwise.
l72 6y ago
That's very true. I run quite a few services on my local network for my family (wireguard, nextcloud, homeassistant, frigate, pihole, jellyfin, bitwarden, ...). While I enjoy setting up and playing with these service, I need to think about managing all these services as little as possible as I don't want to spend all my free time being a system admin. Also, often a new release is not just a system admin task. Sure, it may not be _that_ hard to do a full backup, pull new docker images, spin them up and verify everything. The time sink comes from keeping track of all the releases of all the different projects, reading up about changes, how the upgrade process works, and so on. On top of that, my family has become reliant on several of these services, especially nextcloud and bitwarden. The last thing they want are major changes to it. Long term stability with minimal changes can be a feature!
- BrandoElFollito 6y ago
  I am exactly in the same situation as you (I did not know frigate, but I do not have cameras either - otherwise you listed my main systems). I managed to reduce administration to a minimum by using watchtower to automatically upgrade my containers and using mostly the :latest label. This bit me only twice in a few years: - with the 19-20 migration of Nextcloud, I had one big blank screen when logging in but the synchronization was working. Turns out it was a new default app (something about dashboarding) that was causing it. Googling an fixing took an hour. - with one upgrade of Home Assistant where my devices were not available anymore, there was a problem with the upgrade which they fixed quickly but I have already upgraded. Reading the docs/forum and fixing took an hour. I can live with these two hours across two or three years. I backup /etc on my server with Borg and I know that, worst case, I will recover. I tested this DRP two weeks ago bare metal (recovering to an empty VM from scratch, that is an ubuntu ISO and ultimately getting my encrypted backups from a friend's system -> it really helped to highlight what I was missing)
  - tp3 6y ago
    I'm currently testing a new appliance setup with Nextcloud which includes the ability to use containers as a default for everything, if your container can be moved to an empty VM, nothing gets deleted as I didn't touch it. I would be really happy if this helped.
jcastro 6y ago
> the docker-compose file along with the configuration and data are stored in nextcloud's own dataset. What a great idea!

basilgohar 6y ago

As someone who hosted his own as well, I agree with your sentiment exactly. I've taken down the server that I had hosting my own instance before this, and I am delaying setting up a new one simply because of what you've said here. I imagine that those of us that want that kind of stability are encouraged to go with their hosted offering, but hopefully they'll see the value in having a slower and/or more stable release process. For what it's worth, the upgrade process for the last few major versions went mostly without a hitch for me. I do have to give them credit for that. The only thing I continue to struggle with is the encryption design. I always end-up with some odd state for some files I cannot recover from.

znpy 6y ago
see my sibling comment for an idea on how to set nextcloud up for easy maintenance. disclaimer: i have updated several version, but haven't upgraded to version 21 yet (it just got released)

nmg 6y ago

I am a huge fan of Nextcloud and I couldn't agree more. My upgrade path is to just start a new instance with a fresh sync, because I was traumatized by a turbulent and uncertain upgrade on all of my instances once about two years ago. This is a product I love and choose to rely upon for my data, every day. I'm interested in the bells and whistles and I want the platform to succeed - my preference would be an LTS for my critical data, and the option to spin up newer features separately to test before adoption.

FredFS456 6y ago

In my experience of running my own Nextcloud instance for over 4 years, I've never had an upgrade break my instance. Caveat: I'm on the stable channel and I only update when the client prompts me to update, which is a few point releases into a new release.

kop316 6y ago
That's been my experience as well. I have run Owncloud -> Nextcloud (when it was first released) since at least mid-2015, and I am on the same instance I first built. I stay on the stable channel, and I get a notification if an app or nextcloud itself has an upgrade. The biggest issue is that the "Security & setup warnings" sometimes tells me I need to upgrade my database (and gives me the exact commands to do it) after an upgrade. I will note that the upgrade has taken longer over the years (it used to take 5 minutes, now it can take over 30 minutes), and I think there is an issue with the backing up stage.
- znpy 6y ago
  > I will note that the upgrade has taken longer over the years (it used to take 5 minutes, now it can take over 30 minutes) In their defense, the software has grown a lot and does a lot more things nowadays, it's understandable that the upgrade process takes more.
  - kop316 6y ago
    Yeah, I was assuming it was either that, but I do notice that "backup" takes a long time. As soon as backup is done it is on the order of 4-5 minutes. But then again, I store something like 5 TB worth of files on my Nextcloud, so it could be me as well to.
    - znpy 6y ago
      > I store something like 5 TB worth of files on my Nextcloud Ah, that might be it. IIRC there's a database entry for each file, if you've got a lot of files it might take a while since on upgrade it also run database migrations to adapt to the new schema, that might take a while.

m463 6y ago

I agree - I wish it was more stable and a little less promiscuous. Having your instance have to access the cloud for apps and updates is sort of counter to the "control your own server" sort of mentality. Sort of like docker - do you have to go through their root namespace for everything?

regularfry 6y ago

The answer to that ought to be `apt-get install nextcloud-server` and let the distro maintainers step in, really. Unfortunately because you can't skip versions on upgrade, it's not clear how to cleanly do that.

imwillofficial 6y ago
That’s handled by the package manager.
- regularfry 6y ago
  The package manager would need to have access to the code of all the intermediate versions to run the upgrades safely. That might work for some situations, but it's a hell of an overhead in general.

remram 6y ago

They also raise PHP version requirements. To keep my NextCloud on supported version, I had to update the Linux distribution on my server (was not EOL or anything) to get a PHP that supported versions of NextCloud support... I just wanted to keep getting bug/security fixes for NextCloud.

gog 6y ago
If you are running Debian or Ubuntu use https://deb.sury.org/ https://deb.sury.org/ for PHP.

tcit 6y ago

They can offer that with a subscription.

40four 6y ago

This has spawned a huge thread that I honestly didn't read all of, but someone else mentioned to me they use the 'Community' Snap package. I did not set mine up with this, but it apparently requires a lot less hands on maintenance. In your case you might be interested. https://docs.nextcloud.com/server/21/admin_manual/installation/source_installation.html#installation-on-linux https://docs.nextcloud.com/server/21/admin_manual/installati... https://snapcraft.io/nextcloud https://snapcraft.io/nextcloud Apparently it auto-updates for you, but I'm not sure if it will upgrade major versions, or only security patches.

Forbo 6y ago
The snap does upgrade major versions, although from my experience it tends to be on a delay to ensure stability.
- 40four 6y ago
  Makes sense. Maintenance of self hosted services can be quite annoying, but I guess that’s the price we pay for taking control from the overlords :)

agilob 6y ago

Haha thanks to your comment I noticed I'm using nextCloud 16. I'm going to make a few upgrades now and I'll tell you how it went. Edit: Miration 18->19 is now stuck on Step 4 is currently in process. Please reload this page later. which is downloading zip with new version... Edit2: I restarted installation multiple times, increased pfp-fpm and nginx timeout to 660 seconds and still getting this error. Not today...

cyphar 6y ago
The issues with timeouts can be avoided if you use the command line upgrader: % php /var/www/nextcloud/updater/updater.phar
- agilob 6y ago
  Yea, it didn't work as expected sudo -u nginx php updater/updater.phar Nextcloud Updater - version: v18.0.9-8-g27dac77 Current version is 18.0.14. PHP Fatal error: Uncaught Error: Call to undefined function NC\Updater\curl_init() in phar:///home/owncloud/updater/updater.phar/lib/Updater.php:455 Stack trace: #0 phar:///home/owncloud/updater/updater.phar/lib/Updater.php(119): NC\Updater\Updater->getUpdateServerResponse() #1 phar:///home/owncloud/updater/updater.phar/lib/UpdateCommand.php(147): NC\Updater\Updater->checkForUpdate() #2 phar:///home/owncloud/updater/updater.phar/vendor/symfony/console/Command/Command.php(256): NC\Updater\UpdateCommand->execute() #3 phar:///home/owncloud/updater/updater.phar/vendor/symfony/console/Application.php(820): Symfony\Component\Console\Command\Command->run() #4 phar:///home/owncloud/updater/updater.phar/vendor/symfony/console/Application.php(187): Symfony\Component\Console\Application->doRunCommand() #5 phar:///home/owncloud/updater/updater.phar/vendor/symfony/console/Application.php(118): Symfony\Component\Console\Application->doRun() #6 phar:///home/owncloud/updater/updater.phar/updater.php(10): Symfony\Component\Console\Application->run() #7 /home/owncloud/updater/updater.phar(10): require('...') #8 {main} thrown in phar:///home/owncloud/updater/updater.phar/lib/Updater.php on line 455
  - cyphar 6y ago
    You're missing php-curl (or it's installed but the module is disabled). I'd double-check that you have all of the dependencies of NextCloud installed[1], because php-curl is one of the required dependencies. [1]: https://docs.nextcloud.com/server/21/admin_manual/installation/source_installation.html https://docs.nextcloud.com/server/21/admin_manual/installati...

nucleardog 6y ago

> 1) I upgrade from 17->18->19->20->21 and hope nothing breaks! I've done this since about version 11. And I usually only get around to upgrading every few versions so it's been like... 11->12->13->14, 14->15->16, 16->17->18->19. I do each upgrade one by one. Upgrade, login, check system status and resolve any additional steps it suggests (e.g., adding indices/columns, etc) then jump right into the next upgrade. I've never had one fail on me. Even doing 3-4 major versions at a time it's usually less than a half hour problem.