AFter upgrade one gets htis error: Security & setup warnings Some files have not passed the integrity check. Further information on how to resolve this issue can be found in our documentation. (List of invalid files… / Rescan…) No memory cache has been configured. To enhance your performance please configure a memcache if available. Further information can be found in our documentation. Please double check the installation guides ↗, and check for any errors or warnings in the log. details: 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 ======= - core - EXTRA_FILE - .webapp-owncloud-9.0.0 Raw output ========== Array ( [core] => Array ( [EXTRA_FILE] => Array ( [.webapp-owncloud-9.0.0] => Array ( [expected] => [current] => ) ) ) )
well i guess it's more like a warning but might be worth looking into to avoid confusing people
Same Thing with 9.0.1 version
I confirm the same problem with 9.0.0 and 9.0.1 versions. The problem goes away if I move the file .webapp-owncloud-9.0.0 to some separate location. I wonder if it is possible to store .webapp-* files somewhere else, so they do not interfere with the web server.
There is a discussion on github: https://github.com/owncloud/core/issues/24218
(In reply to Alexey Korepanov from comment #3) > I confirm the same problem with 9.0.0 and 9.0.1 versions. The problem goes [...] and i can confirm this also for v9.0.2
Same problem with nextcloud 9.0.53 : 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 ======= - core - EXTRA_FILE - .webapp-nextcloud-9.0.53 Raw output ========== Array ( [core] => Array ( [EXTRA_FILE] => Array ( [.webapp-nextcloud-9.0.53] => Array ( [expected] => [current] => ) ) ) ) The next releases should correct this problem : Owncloud 9.1 : https://github.com/owncloud/core/pull/25184/commits/a92e13442a7f0c5f0274a9135c24035d026645b8 NextCloud 10 : https://github.com/nextcloud/server/commit/2951a70fcba24417e2873e0fe00696ed185ecf8a Is a backport possible ?
On exempting files from the check , see https://github.com/owncloud/core/issues/22966 * The message only appears if you have admin privs. (confirmed) * There's a config option that switches off the check, but don't do that. (not tried)
This should finally be fixed in the next release: https://github.com/owncloud/core/commit/60e20c71274ab6b3784147533fcf838d9b6fc858
I personally solved this with some apache config settings so that i could have the .well-known outside the actual owncloud/nextcloud directory. So as far as I am concerned this can be closed btw
Indeed, plus in current versions there is a pattern exclusion for us so this should not appear anymore :) Sadly this did not get accepted in nextcloud, but 1 out of 2 is a start
