Update Nextcloud: Move new files in place (Parsing response failed)

[nichierichetti]

Hello everyone,

today I tried to upgrade the version of my nextcloud given the banner in the settings area.
Everything was going well but then it got stuck on Moving new files in place, giving this screen:

The detailed response is simply the HTML of the same page. I don't know what to do because If I refresh that page I am asked for the unhashed updater.secret which I cannot retrieve as OpenSSL is not supported by my hosting service.

What can I do? How can I go on or go back?

[MorrisJobke]

What is in the updater.log in the Nextcloud data directory written? It maybe gives a hint what went wrong here.

[proteus8]

I have the same problem attempting to upgrade from 21.0.0 to 21.0.2. However, there is no updater.log file in the data directory. Further, I am a noob with Nextcloud. Please advise. Thank you.

[proteus8]

I added a updater.log file to the data folder, pressed Retry Update, and got the same message as listed by nichierichetti above. Even after the Retry Update, the updater.log file has a length of 0.

[nichierichetti]

The problem is still ongoing. It happened again with 21.0.7 update.
@Developers are you there?

edit: and if I refresh the page it says:

Authentication
To login you need to provide the unhashed value of "updater.secret" in your config file.

If you don't know that value, you can access this updater directly via the Nextcloud admin screen or generate your own secret:
php -r '$password = trim(shell_exec("openssl rand -base64 48"));if(strlen($password) === 64) {$hash = password_hash($password, PASSWORD_DEFAULT) . "\n"; echo "Insert as \"updater.secret\": ".$hash; echo "The plaintext value is: ".$password."\n";}else{echo "Could not execute OpenSSL.\n";};'

[joshtrichards]

Is your datadirectory located on a different partition than your NC installation directory by chance?

[joshtrichards]

@nichierichetti:

The problem is still ongoing. It happened again with 21.0.7 update.
@Developers are you there?

Yes, a log was requested the same week of your report but we never heard anything back:

#369 (comment)

So, again, please provide the updater.log from your datadirectory which gets written to each time you trigger an update.

In the meantime, the Nextcloud Admin Manual explains how to do:

• an update from the command-line
• a manual update

Both processes can be found in the Maintenance section (see https://docs.nextcloud.com). The most reliable method is the command-line method since some web servers timeout on longer running aspects of the update process. Still other times a manual approach is necessary in environments with unusual filesystems/etc.

@proteus8 Perhaps your datadirectory is configured somewhere else and that's an old spot? Is the contents of the updater-<instanceID> fresh? In the mean time, you can try a command-line update and/or a manual update (see my above comments to the original poster).

[joshtrichards]

Closing due to lack of follow-up with needed details and age.