Nextcloud version: 25.0.5
Operating system and version: Ubuntu 18.02, Docker
Apache Docker image.
I’m running two instances of nextcloud. Both are (as far as I can see) configured exactly the same. Both are running the official docker images. In one instance the Nextcloud Updater in the Admin panel is showing an update to NC 26 although I have configured it to follow the stable channel. The other instance is not showing it. Although I would not update it (because I’m using the docker image) using the updater, it’s annoying that it’s showing the update.
Why could it be that one instance is showing the update and the other not. Where can I look for the issue?
Thanks in advance.
Here are some parts of my config.php
'version' => '220.127.116.11',
'updatechecker' => false,
'updater.release.channel' => 'stable',
'upgrade.disable-web' => true,
'maintenance_window_start' => 1,
Are you expecting NC 26 to not show up as available in the updaters in general? Isn’t it released?
The update servers doesn’t serve new releases to everyone at the same time, so it might be that your other instance just wasn’t “lucky” to get selected yet
Yes, I wasn’t expecting NC 26 to show up, as the website (Release channels - Nextcloud) states for the stable channel the following:
We are very careful about new major releases, usually only making them available after the first minor bug fix release. To update sooner to the new version, use the Beta channel.
I already switched the update channel to beta. Then the new release is advertised in both instances. When I switched back to stable it disappeared in one instance but not in the other.
For what it’s worth, NC 26 is listed as “latest stable” in the documentation.
Sure, it’s not crucial. I wanted to wait for the first minor release and was wondering why one instance is showing the update and the other not.
How does the update is advertised? Is the updater checking for a new release and the instanceid put to a list for being served or not?
In the config snippet you provided you have
updatechecker set to false. Is that, by chance, on the one not showing an available update?
No, that part of the config.php is the same for boht instances. I’s just checked again. Furthermore, this option does not seem to have any effect. In the admin panel it shows that it checks for updates (there is an
i and with mouseover it shows the time of the last check some minutes ago)
Could it be, that if an update was found once (e.g. when being in beta channel), this status is saved/cached somewhere and although it’s not checking again the update possibility is still shown? Where can I look for this cache status if this is the case?