File integrity problems after first install

Expected behaviour

File integrity check passes successfully after initial install

Actual behaviour

See integrity check results here (link below)

Server configuration

Operating system: Ubuntu Mate 20.04

Web server: Apache2

Database: MySQL

PHP version:

ownCloud version: [ownCloud ]10.6.0 (stable)

Updated from an older ownCloud or fresh install: Fresh install

Where did you install ownCloud from: Followed instructions to add PPA to apt and installed from there.

Signing status (ownCloud 9.0 and above): ??

Login as admin user into your ownCloud and access 

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

Seems like the installation process itself led to some integrity problems - appreciate any guidance on the best way to resolve these.

Hi runelynx,

Followed instructions to add PPA to apt and installed from there.

out of curiosity - Which instructions did you follow and which PPA did you use?

Did you try to install with the officiall instructions?


Yes I used that page, clicked Ubuntu and followed the PPA for 20.04.

Ubuntu_20.04 owncloud-complete-files-10.5.0-2+4.1

…then I continued with the steps here:

This is indeed very interesting. I downloaded the package, extracted the owncloud folder and ran an integrity check w/o installing.

At least the twofactor_totp app was signed with a backup file which obviously was removed from the app folder later

$ sudo -u www-data php occ integrity:check-core
ownCloud is not installed - only a limited number of commands are available

  • twofactor_totp:
      • vendor/khanamiryan/qrcode-detector-decoder/tests/QrReaderTest.php~:
        • expected: 05a20a084562bf6a61b9395635b2baa2fa0a3eb443d25027997cc3e83c71d5d1b3dfedd280149071db11121dc1ad30014e4b9778652808c2703b6d642b3b9a68
        • current:

The very same issue was already raised here New fresh OC installation - integrity check failed

I could not reproduce the other file issues, but the current package is definitively broken.

@eneubauer: would you like to forward this to someone who is packaging ownCloud?


Thanks for highlighting, I forwarded it to the appropriate team, however it seems like this is a problem that could potentially take a little longer to resolve.