Upgrade from 12.0.4 to 12.0.5/13xxx is not possible

🚧 Installation
,
1

Hi,

I tried to update my installation via the updater, but it stopps at the first point “Initializing / Current version is 12.0.4.”. Nothing else happens. If I open the log file (updater.log) I get the following entries:

2018-02-08T23:36:59+0800 142XdSzAOT [info] request to updater
2018-02-08T23:36:59+0800 142XdSzAOT [info] currentStep()
2018-02-08T23:36:59+0800 142XdSzAOT [info] show HTML page
2018-02-08T23:36:59+0800 142XdSzAOT [info] current version: 12.0.4 build time: 2017-12-04T07:21:01+00:00 c772810ecabce06f45dea16b7c67185c90df4a0d
2018-02-08T23:36:59+0800 142XdSzAOT [info] getUpdateServerResponse()
2018-02-08T23:36:59+0800 142XdSzAOT [info] updaterServer: https://updates.nextcloud.org/updater_server/
2018-02-08T23:36:59+0800 142XdSzAOT [info] releaseChannel: production
2018-02-08T23:36:59+0800 142XdSzAOT [info] internal version: 12.0.4.3
2018-02-08T23:36:59+0800 142XdSzAOT [info] updateURL: https://updates.nextcloud.org/updater_server/?version=12x0x4x3xxxproductionxx2017-12-04T07%3A21%3A01%2B00%3A00+c772810ecabce06f45dea16b7c67185c90df4a0dx7x1x12

What’s wrong with my installation? The server ist connected to the internet and can access the internet. The installation of apps is possible without problems.

Michael

2

you have chosen the most stable release-channel. which is always behind a bit but pretty well tested as well.

if you wanna upgrade a bit faster than “production” set your channel to “stable”… this should solve your upgrade-problem…

but remember: someone (maybe you yourself) had set the channel to “production” before - and maybe there was a good reason for it.

3

Hi,

I just changed the channel to “stable” but the problem persists. :frowning:

Michael

4

let’s wait a bit - 12.0.5 should be available for you if you’re updating from 12.0.4.

aww… let’s hope that you’re not running a docker or a snap-version.

5

@m8ichael
Cloud you solve the problem?
I have the same problem when I try to upgrade from 12.0.5 to 13.0.0.

6

No, I could not solve it yet. The updater doesn’t work. :frowning:

7

I finally managed to come one step further. In my case the updater could not download files from *.nextcloud.org. So if you have a firewall that restrict your internet access you probably want to whitelist access to *.nextcloud.com and *.nextcloud.org. If the updater cannot download files from those domains it will fail without printing any error message! Damn PHP! In Java you would at least get an IOException or something similar. Why can PHP not be like Java. :frowning: