You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Set log level to debug
Turned on maintenance mode
Updating database schema
Updated database
UnexpectedValueException: The files of the app "user_external" were not correctly replaced before running the update
Update failed
Maintenance mode is kept active
Reset log level
After patching apps/user_external/appinfo/info/xml
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
Nextcloud configuration:
Config report
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
or
Insert your config.php content here.
Make sure to remove all sensitive content such as passwords. (e.g. database password, passwordsalt, secret, smtp password, …)
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)
LDAP config
With access to your command line run e.g.:
sudo -u www-data php occ ldap:show-config
from within your Nextcloud 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
Browser:
Operating system:
Logs
Web server error log
Web server error log
Insert your webserver log here
Nextcloud log (data/nextcloud.log)
Nextcloud log
Insert your Nextcloud log here
Browser log
Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...
The text was updated successfully, but these errors were encountered:
Steps to reproduce
Expected behaviour
Upgrade success
Actual behaviour
After patching apps/user_external/appinfo/info/xml
I can continue with the upgrade. The app isn't updated for 13 yet https://github.com/nextcloud/apps/blob/master/user_external/appinfo/info.xml
Server configuration
Operating system: FreeBSD 11.1-p1 amd64
Web server: Apache 2.4.29 HTTP/2
Database: MariaDB 10.2.10
PHP version: 7.1.11
Nextcloud version: 13.0.0beta1
Updated from an older Nextcloud/ownCloud or fresh install:
Updated from 12.0.3
Where did you install Nextcloud from:
FreeBSD package, generated from https://download.nextcloud.com/server/prereleases/nextcloud-13.0.0beta1.bz2
Signing status:
Signing status
Technical information
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.
Results
Raw output
Array
(
[twofactor_totp] => Array
(
[INVALID_HASH] => Array
(
[appinfo/info.xml] => Array
(
[expected] => 74790f511d0da5d40ea352f690032db642cf211c1ef971bd7a3eaf376e479fe55c86257383a448260219cf662faad1d6757309786b93dc9fabb20d4d2f02a7a7
[current] => 14a3e8e93dbf88af3201de9cc3c898dafbc1cfc72f510956e2481497519c5bebf95198bbaf39b0becfe491ff8783e59618ff48e9b45ce6b432cd04d2b5228491
)
)
List of activated apps:
App list
Nextcloud configuration:
Config report
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)
LDAP config
Client configuration
Browser:
Operating system:
Logs
Web server error log
Web server error log
Nextcloud log (data/nextcloud.log)
Nextcloud log
Browser log
Browser log
The text was updated successfully, but these errors were encountered: