Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-logging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the health-check domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/wp-includes/functions.php on line 6114 Get up-to-date with the new Nextcloud updater - NextcloudSkip to main content
However, as they lack the new updater, versions before 9.0.54 currently receive no update notifications. Neither do the have an easy way to update via the built-in updater. As there are still a significant number of users on Nextcloud 9.0.53 and these users are potentially at risk of security breaches and missing stability bugs, we devised an easy way to upgrade to a newer release. Users of 9.0.53 and older will receive a notification pointing to this blog so they can follow the steps and get to a new Nextcloud, easily and safely.
Seven steps
To upgrade an older Nextcloud system without manually having to extract and replace the files, follow these instructions:
1. Log into your server with SSH or FTP and go to the folder where Nextcloud is installed, for example /srv/www/htdocs/nextcloud
2. Delete the file updater/index.php. The folder updater/ can be found in the subfolder of the folder where you installed your Nextcloud.
3. Create a new file updater/index.php. Copy-paste this content into it and save it.
4. Add the following at the end of your /config/config.php file, right before the line consisting of );: 'updater.server.url' => 'https://updates.nextcloud.com/updater_server/',
5. Log into Nextcloud. In your admin panel go to the updater section and switch to the channel “production” and then to “stable”. This ensures that your update cache is cleaned.
6. Reload the admin page with F5. You should now see an update notification to the Nextcloud 10 release. Scroll down to the “Updater” section and follow the instructions in the updater app.
7. When upgraded, remove the updater.server.url line that you’ve added to /config/config.php
Congratulations! Now you are on an up-to-date version with a properly working updater including update notifications for the admin account.
Those who prefer to do the entire process from the command line can grab this file, put it in the updater subfolder of Nextcloud and run it with php updater.phar
If you run the command but get no output whatsoever, check if you have the php-phar module is installed on your system. You can check by running php -m | grep -i Phar and looking at the output. If you get nothing, phar is not installed. You have to install it, running zypper in php7-phar or the equivalent for your distribution. Once you get notified that there is a new version, follow the instructions to install it.
We apologize for the inconveniences caused by the broken updater and are constantly working on improving the updater experience. And your help is welcome! If you manage to discover a bug in our new updater while upgrading to Nextcloud 11 Release Candidate you can earn a free T-Shirt.
“When we have welcoming communities of contributors, open source software gets better and more useful to everyone.” Limor Fried, Electrical Engineer, Inventor and Founder of open-source hardware company Adafruit We believe in this ideal and love to work with our community. We are always looking to involve more people in Nextcloud, bringing in their ideas, […]
When cables are cut, sanctions are put in place or privacy legislation prohibits the use of the service your entire organization depends on, what can you do? Amidst geo-political changes, organizations face dependencies on large, centralized communication platforms. A major example of this is the SaaS-only communication platform Microsoft Teams. It is the only solution […]
In Nextcloud Hub 8, we introduced interactive widgets, a completely new mechanic that lets you share, access and interact with items from various apps in a compact widget format throughout your platform.
We save some cookies to count visitors and make the site easier to use. This doesn't leave our server and isn't to track you personally!
See our Privacy Policy for more information. Customize
Statistics cookies collect information anonymously and help us understand how our visitors use our website. We use cloud-hosted Matomo
Matomo
_pk_ses*: Counts the first visit of the user
_pk_id*: Helps not to double count the visits.
mtm_cookie_consent: Remembers that consent for storing and using cookies was given by the user.
_pk_ses*: 30 minutes
_pk_id*: 28 days
mtm_cookie_consent: 30 days