@tflidd ,
Successful upgrade from 10.0.1 -> 10.0.2!
Here is what to expect.
Web Updater
The attempt to use the web interface failed. Time was spend trying to resolve the failed web interface upgrade.
However, when clicking on the notification update bell with the red dot on it and then hovering over the item to be updated, the INCORRECT server is shown in the tool tip display.
In fact the INCORRECT server is actually the first server used in the INITIAL setup of config.php:
‘trusted_domains’=> array (0=> ‘first_server’, 1=>others, 2=>another) which is no longer used.
Now config.php is using ‘trusted_domains’=> array (0 => ‘new_server’,).
It appears the web updater is obtaining the (target) server (in this case first_server) from a memory location that is stuck with the INITIAL setup value (first_server) which in many cases is no longer used.
Manuel Updater
Manual Nextcloud Upgrade — Nextcloud 10 Server Administration Manual 10 documentation
https://docs.nextcloud.com/server/10/admin_manual/maintenance/manual_upgrade.html
Always start by making a fresh backup and disabling all 3rd party apps.
Put your server in maintenance mode. This prevents new logins, locks the sessions of logged-in users, and displays a status screen so users know what is happening. There are two ways to do this, and the preferred method is to use the occ command, which you must run as your HTTP user. This example is for Ubuntu Linux:
sudo -u www-data php occ maintenance:mode --on
The other way is by entering your config.php file and changing ‘maintenance’ => false, to ‘maintenance’ => true,.
With only maintenance:mode --on: a splash screen appeared with a update button when an attempt was made to login. With both maintenance locks set:
** maintenance:mode --on and maintenance’ => true, then logins are not allowed.**
Also, the android app is able to access the nextcloud server even with maintenance: mode --off and maintenance=>true
- Back up your existing Nextcloud Server database, data directory, and config.php file.
(See Backing up Nextcloud.)
1a. Step 5 will be another back up for data/ and config.php. But another backup for data/ and
config outside the server would not hurt. Do it!
1b. Here is how to back up the database per the instructions. Please do this backup!
mysqldump --lock-tables -h [server] -u [username] -p[password] [db_name] > nextcloud-sqlbkp_date +"%Y%m%d".bak (There is NOT a space after the “+”) and backticks `
If everything goes well in step 10, the database backup will not be needed but. If something
goes wacky then restoring the database will be necessary
2.Download and unpack the latest Nextcloud Server release (Archive file) from
nextcloud.com/install/ into an empty directory outside of your current installation.
To unpack your new tarball, run: tar xjf nextcloud-[version].tar.bz2
3.Stop your Web server. For example:
Fedora: systemclt stop httpd
Ubuntu: systemctl stop apache2
4.Rename your current Nextcloud directory, for example nextcloud-old.
Very good idea.
5.Unpacking the new archive creates a new nextcloud directory populated with your new
server files. Copy this directory and its contents to the original location of your old server.
For example /var/www/, so that once again you have /var/www/nextcloud.
The original location of your old server will look like this
/var/www/
…nextcloud <— new version
…nextcloud-old <---- old version
6.Copy the config.php file from your old Nextcloud directory to your new Nextcloud directory.
7a. If you keep your data/ directory in your nextcloud/ directory, copy data/ from your old
Nextcloud directory to your new nextcloud/ directory.
7b. If you keep it (data/) outside of nextcloud/ then you don’t have to do anything with it.
8a. If you are using 3rd party applications, look in your new nextcloud/apps/ directory to see if
they are there. If not, copy them from your old apps/ directory to your new one. Make sure the
directory permissions of your third party application directories are the same as for the other
ones.
8b. Make sure files have correct ownership (your location may be different than /var/www)
Fedora: chown -R apache:apache /var/www/nextcloud
Ubuntu: chown -R www-data:www-data /var/www/nextcloud
9.Restart your Web server.
Fedora: systemctl restart httpd
Ubuntu: systemctl restart apache2
10.Now launch the upgrade from the command line using occ, like this example on Ubuntu
Linux.
Make sure you are in /nextcloud location i.e /var/www/nextcloud. That is where occ is!
sudo -u www-data php occ upgrade
11.The upgrade operation takes a few minutes to a few hours, depending on the size of your installation. When it is finished you will see a success message, or an error message that will tell where it went wrong.
This manual upgrade went smooth. I plan to upgrade 10.0.2 -> 11.0.0 using these notes
10.0.2 -> 11.0.0 did not product the pretty blue folder icons next to files