Nextcloud

From BITPlan Wiki
Revision as of 20:36, 28 December 2017 by Wf (talk | contribs) (→‎Step 1)
Jump to navigation Jump to search

Upgrading from owncloud 9.0.0 to latest Nextcloud

It 2017-12 and we had been using owncloud 9.0.0 for some time on our old server. Now we wanted to migrate to Nextcloud.

Step 1

Copying everything from old server to new server

/usr/share$ tar cvfz owncloud.tgz owncloud/
  1. copy the tgz file to the new server and unpack at /usr/share
  2. to a mysqlump of the owncloud mysql database on the old server
  3. create a new owncloud mysql database on the new server
  4. use the dump to restore the data on the new server
  5. copy the apache configuration from the old server to the new server and activate it
  6. modify the config.php to fit the new server

At this point things to frustrating We ran into the owncloud issues:

Internal Server Error
The server encountered an internal error and was unable to complete your request.
Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
More details can be found in the server log.
Technical details
    Remote Address:
    Request ID: ...
root@server:/usr/share/owncloud/data# tail -1 owncloud.log 
{"reqId":"...","remoteAddr":"","app":"index","message":"Exception: {\"Exception\":\"Exception\",\"Message\":\"The requested uri() cannot be processed by the script '\\\/owncloud\\\/index.php')\",\"Code\":0,\"Trace\":\"#0 \\\/usr\\\/share\\\/owncloud\\\/lib\\\/private\\\/appframework\\\/http\\\/request.php(636): OC\\\\AppFramework\\\\Http\\\\Request->getRawPathInfo()\\n#1 \\\/usr\\\/share\\\/owncloud\\\/lib\\\/base.php(828): OC\\\\AppFramework\\\\Http\\\\Request->getPathInfo()\\n#2 \\\/usr\\\/share\\\/owncloud\\\/index.php(39): OC::handleRequest()\\n#3 {main}\",\"File\":\"\\\/usr\\\/share\\\/owncloud\\\/lib\\\/private\\\/appframework\\\/http\\\/request.php\",\"Line\":610}","level":3,"time":"2017-12-28T09:06:17+00:00"}

That was a known issue that seems not to be fixed - the bug report was simply closed:

So we deciced to migrate/upgrade to Nextcloud

Step 2 - migration to nextcloud

We followed the instructions at:

Which worked like a charm.