Upgrade from 10.2.1 to 10.3.0 using Upgrader in Owncloud Web Interface

Steps to reproduce

  1. Manually installed version of 10.2.1
  2. Configure read and write permissions on config.php.orig
  3. Use Upgrader App in Owncloud Interface
  4. Upgrade completes successfully
  5. Access login page for Owncloud Web Interface on frontend
  6. Error message displays (see attached screenshot)

Expected behaviour

After install is successfully. User should be able to access and see login screen with login fields to login.

Actual behaviour

An error message displays install. See attached screen shots

Server configuration

Operating system:

  • CENTOS 6.10 [dedicated17] * [ v84.0.9]

Web server:


PHP version:

ownCloud version: (see ownCloud admin page)

Updated from an older ownCloud or fresh install:

Where did you install ownCloud from:
manual install

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) ...


i think the same answer as given in the topic below is valid for situation as well:

@shinshuri Maybe you could also provide some background information or even suggestions in Brainstorming on "Repair warning: You have incompatible or missing apps enabled that could not be found or updated via the marketplace." message improvements why the message is unclear or how to improve this so that you could have immediately see the required steps to continue with the update?

Thanks. I resolved this issue. After posting.

1 Like

Hi Tom42:

I had our IT Support update Owncloud manually upgrade our Owncloud 10.9.X version to 10.2.1 a couple of weeks ago. Then, you released 10.3.0. 1) I disabled all market place apps before attempting the upgrade. 2) I attempted to upgrade using the Updater Button in Web Interface. 3) The config file permissions were not set to allow the Updater to process. 4) We changed the permissions on the config file as shown in the first screenshot. 5) After the update completed. System auto showed installed successfully. 6) System automatically redirected to the login screen and the second screen appeared. Stating instance is in maintenance, when it should have been completed and the login screen should have displayed. 7) We disabled the maintenance mode manually and the second screen displayed. 8) I am not sure why the message appeared when we disabled all marketplace apps before attempting the installation. I hope this explanation works for you. Let me know.

1 Like