Migrating owncloud from VMWare 5.5 to 6.5


I have migrated owncloud from Hyper-V to VMware ESXi 5.5 server with no issues other than having to recreate the network adapter. I am now trying to migrate it to ESXi 6.5. The migration seem to succeed but could not connect to server via the web link? I was able to ping various computers but web link just lists generic 500 Internal Error. Has anyone done a migration like this before and know how I can troubleshoot.

Here is some information. I have inherited the server so I am not well versed on Ubuntu or OwnCloud:

  1. It is a OwnCloud 8.2.7 server
  2. Ubuntu is 14.05

Let me know if any other details will help to troubleshoot. I did the migration while the server was online. Another option would be to install a new Owncloud server and migrate data. If someone can give me the steps to do that it may be faster than migrating.

Any help would be appreciated…

Steps to reproduce

Expected behaviour

Tell us what should happen

Actual behaviour

Tell us what happens instead

Server configuration

Operating system:

Web server:


PHP version:

ownCloud version: (see ownCloud admin page)

Updated from an older ownCloud or fresh install:

Where did you install ownCloud from:

Signing status (ownCloud 9.0 and above):

Login as admin user into your ownCloud and access 
paste the results into https://gist.github.com/ and puth the link here.

The content of config/config.php:

Log in to the web-UI with an administrator account and click on
'admin' -> 'Generate Config Report' -> 'Download ownCloud config report'
This report includes the config.php settings, the list of activated apps
and other details in a well sanitized form.


If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your ownCloud installation folder

*ATTENTION:* Do not post your config.php file in public as is. Please use one of the above
methods whenever possible. Both, the generated reports from the web-ui and from occ config:list
consistently remove sensitive data. You still may want to review the report before sending.
If done manually then it is critical for your own privacy to dilligently
remove *all* host names, passwords, usernames, salts and other credentials before posting.
You should assume that attackers find such information and will use them against your systems.

List of activated apps:

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your ownCloud installation folder.

Are you using external storage, if yes which one: local/smb/sftp/…

Are you using encryption: yes/no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/…

LDAP configuration (delete this part if not used)

With access to your command line run e.g.:
sudo -u www-data php occ ldap:show-config
from within your ownCloud installation folder

Without access to your command line download the data/owncloud.db to your local
computer or access your SQL server remotely and run the select query:
SELECT * FROM `oc_appconfig` WHERE `appid` = 'user_ldap';

Eventually replace sensitive data as the name/IP-address of your LDAP server or groups.

Client configuration


Operating system:


Web server error log

Insert your webserver log here

ownCloud log (data/owncloud.log)

Insert your ownCloud log here

Browser log

Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log 
c) ...


Server Configuration
OS: Ubuntu 14.04.5
Web Server: Apache(Best guess)
Database: ??
PHP Version: php5 (Guess)
Owncloud version: 8.2.7
in /var/www/html have 3 folders owncloud owncloud2 owncloud3 (Not sure Why)


As far as I know, the update of the VM shouldn’t cause problems for ownCloud as long as ownCloud can be accessed normally. If it’s an external link, maybe you can’t access because the DNS or ip address doesn’t match any longer with the VM

First of all, check and understand your setup. Under normal circumstances, you should have more than one ownCloud directory in the server. If you have more, check the configuration and the data directories of all of them in order to check if they share both directories.

If they don’t share the directories, I guess they’re different installations. You should be able to remove the installations that aren’t in use.
If they share the directories, all of the installations might share the same data, but the code running could be different. It’s usually fine as temporary measure, but DB structure might change between versions, so always have a backup of the DB just in case.

Once you’ve figure out what installation are you using, we’ll need the logs (the owncloud.log file is usually located in the owncloud’s data directory)

Note that you should consider to update the ownCloud’s installation to a newer one because 8.2.x is no longer maintained.