{"id":1208,"date":"2019-04-14T22:01:35","date_gmt":"2019-04-14T20:01:35","guid":{"rendered":"http:\/\/hobbykeller.spdns.de\/?p=1208"},"modified":"2019-05-16T14:32:20","modified_gmt":"2019-05-16T12:32:20","slug":"updating-nextcloud-via-updater-gui","status":"publish","type":"post","link":"https:\/\/hobbykeller.spdns.de\/?p=1208","title":{"rendered":"Updating Nextcloud via Updater GUI"},"content":{"rendered":"\r\n

While the updater GUI is really comfortable, I regularly run into difficulties with file permissions and timeouts. This post summarizes the steps needed to run an update via Nextclouds Update GUI successfully.<\/p>\r\n\r\n\r\n\r\n

<\/p>\r\n\r\n\r\n\r\n

1. Acquire su privileges and produce a fresh backup<\/h1>\r\n\r\n\r\n\r\n

This step contains preliminary work and the removal of the assets<\/a> directory which is normally empty but causes the Updater to stall immediately.<\/p>\r\n

sudo su\r\ncd \/var\/www\/\r\nrm -rf oldcloud\r\ncp -R owncloud oldcloud\/\r\nrm -rf owncloud\/assets<\/pre>\r\n
2. Set ownership to www-data<\/h1>\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
This step is needed to prevent the Nextcloud updater from failing the file and directory permissions check:<\/p>\r\n
chown -R www-data:www-data owncloud\/<\/pre>\r\n
In case the check still fails, you can set file permissions as follows (takes a while to perform on my Pi ZeroW):<\/p>\r\n
find \/var\/www\/owncloud -type d -exec chmod 755 {} \\;\r\nfind \/var\/www\/owncloud -type f -exec chmod 644 {} \\;<\/pre>\r\n\r\n\r\n\r\n
3. Increase timeout of Nginx<\/h1>\r\n\r\n\r\n\r\n
To prevent Nginx from running into a timeout during the creation of the backup, you have to edit \/etc\/nginx\/nginx.conf<\/code>. Uncomment the fastcgi_read_timeout<\/code> parameter and increase it from 600<\/code> to 6000<\/code>.<\/p>\r\n\r\n\r\n\r\n
Do not forget to reload the new configuration settings of Nginx by<\/p>\r\n
service nginx reload<\/pre>\r\n
In case, the update still fails, also try to uncomment and modify the parameter proxy_read_timeout<\/code> in the same way as above.<\/p>\r\n\r\n\r\n\r\n
4. Start the updater web service<\/h1>\r\n\r\n\r\n\r\n
Log in as admin on your Nextcloud GUI navigate to the update pane click on “Start Update” in the Updater. The Update should now run through without any problems.<\/p>\r\n\r\n\r\n\r\n
At the end of the update procedure, choose to switch off maintenance mode. In case this does not happen automatically, you can switch it off via console:<\/p>\r\n
sudo -u www-data php \/var\/www\/owncloud\/occ maintenance:mode --off<\/pre>\r\n
5. Finalize Update by reopening the Login home page<\/h1>\r\n\r\n\r\n\r\n
Use your browser of your desktop to navigate to the Nextcloud login page. It may be that you have to trigger the finalization of the update by clicking some button like “Finish update”. This will take another couple of minutes.<\/p>\r\n\r\n\r\n\r\n
To be on the safe side, log in with your administrator account and go to the Settings, choose “Overview” from the “Administration” section on the left side of the window and check the Security and Setup warnings.<\/p>\r\n
Keep in mind though, that not all warnings require immediate action:<\/p>\r\n