-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: NC 25 error when trying upgrade from beta 7 to RC1 with GUI #34201
Comments
I found a work around cd into your nextcloud updater dir /updater/ mine was /var/www/nextcloud/updater/ then run sudo -u www-data php updater.phar |
Had the same problem. Updated manually via shell. |
Able to move past with these commands..... |
Same issue from RC1 to RC2 also reported it here https://help.nextcloud.com/t/sixth-beta-of-nextcloud-25/145306/17?u=andyxheli |
Looks like its been fixed in RC2. Please see post from below link https://help.nextcloud.com/t/25-0-0rc2-24-0-6-23-0-10/146473 |
@blizzz im on RC2 going to RC3 and still having this issue. i not you mentioned it should be fixed in RC2 |
The issue with the forgotten .step file was fixed in RC3. I am actually not sure where this comes from, yet, but it definitely needs a fix. Would recommend the cli update as workaround, or follow the instructions. |
Okay, sounds good. Thanks for the update. We'll do the workaround for now. Until further notice. |
I't doesn't work via shell, i got this error message: Any idea? |
try the following I found a work around cd into your nextcloud updater dir /updater/ mine was cd /var/www/nextcloud/updater/ then run sudo -u www-data php updater.phar |
Thanks, but my post is the result when i do exactly this ^^Am 07.10.2022 um 20:03 schrieb Andy Xheli ***@***.***>:
@depesch
try the following
I found a work around cd into your nextcloud updater dir /updater/ mine was
cd /var/www/nextcloud/updater/
then run
sudo -u www-data php updater.phar
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Oh i see sorry about that. Hmmmm try running an |
The fix should come with the next RC. If you like to give it a try and have sed installed on your server, your may run
from within your Nextcloud root directory. Afterwards, with a hard refresh on the admin settings overview page, updater should work again upon clicking "Open Updater". |
was not fixed with RC3, im on RC3 and get this issue if i try to go to RC5
|
manually searched for ".token" in dist/updatenotification-updatenotification.js and removed it. Webupdater seems to work now |
Bug description
When i try to upgrade using GUI from 25 beta 7 (25.0.0.11) to 25 RC1 there some strange information appeared asking for password from config file. I did copy & paste the secret, but it didn't work like it would ignore LOGIN button (it didn't show/did anything).
Also updating from command line (terminal) did worked well.
Steps to reproduce
Expected behavior
It should just start upgrade page.
Installation method
Community Manual installation with Archive
Operating system
RHEL/CentOS
PHP engine version
PHP 8.1
Web server
Nginx
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 22.2.3 to 22.2.4)
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
I'm using RHEL 9, on 64-bit CPU, with 64G RAM.
nginx -v
nginx version: nginx/1.20.1
php81 -v
PHP 8.1.10 (cli) (built: Aug 30 2022 16:09:36) (NTS gcc x86_64)
Copyright (c) The PHP Group
Zend Engine v4.1.10, Copyright (c) Zend Technologies
with Zend OPcache v8.1.10, Copyright (c), by Zend Technologies
mariadb --version
mariadb Ver 15.1 Distrib 10.5.16-MariaDB, for Linux (x86_64) using EditLine wrapper
uname -a
Linux zzz-NAS 5.14.0-70.26.1.el9_0.x86_64 #1 SMP PREEMPT Fri Sep 2 16:07:40 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: