Due to a regression in creating multiple share links we had to pull NC 28.0.13 and 30.0.3. We will follow up with a hot fix release asap.
It appears that this may have in part affected my update and the installation that I’m in charge of. Do we know if anything has happened with this, or if the update troubles over the past month have been looked at?
I’m not in a rush, I’m just curious right now since I’m probably going to be spending part of January learning how to reinstall.
Both 30.0.3 and 28.0.13 have already been replaced with 30.0.4 and 28.0.14:
yeah, but did that fix the update path? Beginning of Dec. updates didn’t seem to be working, and that was when this was announced. I don’t really trust the update process at this point anyway, but it would have been good if the announcement that says a hotfix will be coming actually has the info that says “we fixed it”.
I was looking at the feed that announced that these releases were pulled, and nothing was mentioned that this issue was resolved. Therefore I can only assume that it’s still broken.
What fix for “the update path” are you referring to? Keep in mind there are many ways of both deploying and updating Nextcloud. You may need to provide additional context, especially if you’re referring to something that is package specific rather than in Nextcloud Server itself.
I have a bone stock install of (AIO) Next Cloud v. 27.1.7 if I go into the AIO interface and do the off/on restart/update it breaks. I can follow the recovery instructions, but they only work once, after that I need to take additional steps to fix the install. Doesn’t matter what else I do, AIO updates break my installation.
Apparently if you don’t update for a few months, then this is the expected result. At the same time that I ran into this, I got info in this forum that there might be an issue in the update script, also these above mentioned versions were removed from the update path, thus my question since that might be part of why I was unable to reliably update my installation. It’s rapidly becoming apparent that the AIO update process may be the issue and considering the questions I’ve seen elsewhere, updating Next Cloud is only easy if you install the latest version and update every couple of days.
As to there being several ways to update, that might be part of the issue. I have not yet found a definitive way to update that reliably works 100% of the time. I’m pretty much resigned to the fact that I have to reinstall again.
Hi, I just wanted to point out that there was indeed a bug in the update logic when upgrading between multiple major versions that was fixed and released with AIO v10.1.0: nextcloud entrypoint: fix missing apostroph in require command by szaimen · Pull Request #5718 · nextcloud/all-in-one · GitHub
Now as stated in the docs, upgrading should work even if one missed a major version and should thus enable updates for ca. 6 months.
However there is still this manual upgrade documentation if you dont upgrade for 6+ months which allows you to get back on track: all-in-one/manual-upgrade.md at main · nextcloud/all-in-one · GitHub
If you do not update Nextcloud AIO for a long time (6+ months), when you eventually update in the AIO interface you will find Nextcloud no longer works. This is due to incompatible PHP versions within the nextcloud container. There is unfortunately no way to fix this from a maintainer POV if you refrain from upgrading for so long.
The only way to fix this on your side is upgrading regularly (e.g. by enabling daily backups which will also automatically upgrade all containers) and following the steps below to get back to a normal state:
…
Recently, a friend of mine was in the very same situation but was able to follow the documentation mentioned here which allowed him to get back to a working state. Now, he enabled daily backups and automatic container updates which solves all his problems he had by not upgrading for a very long time.
not sure what extra instructions you gave your friend, but this upgrade breaks my installation. Here are a few things I had trouble with based on your upgrade instructions located here all-in-one/manual-upgrade.md at main · nextcloud/all-in-one · GitHub
Method 1
#2 this version check doesn’t give expected results. I saw this:
if (PHP_VERSION_ID >= 80300) { http_response_code(500); echo 'This version of Nextcloud is not compatible with PHP>=8.3.<br/>'; echo 'You are currently running ' . PHP_VERSION . '.'; exit(1);
So something in the nextcloud docker container is not doing what it should.
#7 make sure that there is no skip.update file in the Nextcloud datadir. I don’t have any information about where to start looking for this. I think I was looking in the right spot, but on a default installation, I should at least be given a hint.
Also:
You can open the Nextcloud container logs with sudo docker logs -f nextcloud-aio-nextcloud
And no info as to what I should look for, as it is, everything looks normal, but I don’t see any information about which version.
#8 simply restart the container again with sudo docker restart nextcloud-aio-nextcloud until it does not install a new Nextcloud update anymore
And how am I supposed to tell? I don’t see anything in the log files, docker ps -a doesn’t show any change, and the command itself is silent. I ran the command about 10 times with no change in how long it took. It was much faster than the previous step, so I will assume that it’s up to date.
#9 using the AIO interface again. Except now it’s saying there’s an update and that I need to restart something there to get it working. So I did that, but after trying to restart the containers in AIO, I get the same error as before when I tried to restart the containers without doing this complex method.
So is there something missing? I tried this before and got the same results, so I’m not sure where I’m supposed to look to resolve this. The command in #8 doesn’t give me the results I would expect. There is no feedback from the command, no errors, but when I look at what docker says, it says it’s working, but in AIO, it says “starting” It never does finish starting though.
After manually stopping all containers, I can get control again in AIO interface, but trying to start sends it into the broken loop again.
And when I check the logs as listed in #7 I get the same error I started with:
Connection to nextcloud-aio-redis (172.18.0.5) 6379 port [tcp/redis] succeeded! This version of Nextcloud is not compatible with PHP>=8.3.<br/>You are currently running 8.3.14.It seems like your installed Nextcloud is not compatible with the by the container provided PHP version. This most likely happened because you tried to restore an old Nextcloud version from backup that is not compatible with the PHP version that comes with the container. Please try to restore a more recent backup which contains a Nextcloud version that is compatible with the PHP version that comes with the container. If you do not have a more recent backup, feel free to have a look at this documentation: https://github.com/nextcloud/all-in-one/blob/main/manual-upgrade.md
I don’t think it updated anything.
It looks how I’d expect if you’re stuck on v27 (which is what you stated so makes sense to me).
Also matches up with what is described in the docs for v27.
So the max supported version for v27 is PHP 8.2.
What PHP version did you specify for Method 1 Step 5 when you attempted the manual upgrade?
I was able to get it restarted on PHP8.1
But when I do, all I see is that my installation is out of date and needs to be updated, but updating breaks my installation.
Everything I’ve found in searching says that all-in-one/manual-upgrade.md at main · nextcloud/all-in-one · GitHub is supposed to update your installation. Does this not upgrade from one version to the next? Am I force to do a reinstall every time there is a new version?
Also, in #8 where it says:
“After the Nextcloud container is started (you can tell by looking at the logs), simply restart the container again with sudo docker restart nextcloud-aio-nextcloud until it does not install a new Nextcloud update anymore upon the container startup.”
Am I supposed to see something? I never see it do anything other than stop the container and start it again. No indication that anything is updated.
BTW, it’s broken again, so I have to figure out how to get it working.
well, looks like I have to reinstall now. I’ve managed to delete the nextcloud-aio-nextcloud container and don’t have a copy of the /tmp/nextcloud-aio-nextcloud file to recreate the container.