Closed Mediaf closed 6 months ago
This may be related to nextcloud/updater#90 which we should probably confirm and merge...
So for all versions from 20 to 25, i had to update nextcloud by hand and it's a bit boring
Do you a mean fully manual installation or simply running the updater
from the CLI instead of the web UI?
The parsing matter should only impact web-based runs I believe...
Hello, Thanks for your answer. I had to do a full install, like a new one : download the next release archive, unzip it to the server, copy it to the nextcloud path, change the owner to apache:apache, then open the homepage to do the update. For me, the problem seems to be that the updater doesn't understand the returned value {"proceed":true} because it is html encoded.
As a note, I also get this error on step 5. There it is caused by a too low PHP memory limit (as indicated by several forum threads). Increasing this limit and deleting the .step file solved it for me.
Duplicate of nextcloud/updater#88
⚠️ This issue respects the following points: ⚠️
Bug description
Each time I try to update from version to the next proposed since version 21, I'm stuck in the page "updater" At each step I get an error "Parsing response failed." When I click on "Show detailed response", I see an html encoded text explaining the response, but the tool doesn't seems to understand this response because of the html syntax for example on "Check for write permissions", the detailed response is :
{"proceed":false,"response":["\/var\/www\/html\/nextcloud\/updater\/..\/.htaccess","\/var\/www\/html\/nextcloud\/updater\/..\/.user.ini"]}
because my .htaccess and .user.ini files aren't owned by the apache user
But the worst problem is that when one step is successful, I'm also blocked and I get "Parsing response failed" while the detailed response is
{"proceed":true}
I don't understand why the response is html encoded and why the tool doesn't understand it. I managed to pass some steps, but when I come to "Delete old files", the updater definitively stops 'cause it has'nt anymore code to execute !
So for all versions from 20 to 25, i had to update nextcloud by hand and it's a bit boring
Steps to reproduce
1.Click on "open updater system"
Expected behavior
The updater should run from the start to the end without be blocked
Installation method
Other Community project
Nextcloud Server version
25
Operating system
RHEL/CentOS
PHP engine version
PHP 7.4
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response