-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrity check false alert on fresh installation #5578
Comments
A timing issue then - as a rescan happens automatically after some time anyway, I'm not sure we have to do anything here. |
While this is not the highest priority, I think it should be addressed as this may give false impression the installation is i.e. "doctored" |
@LukasReschke anything we can/should do here? |
How did you do that automated installation? The file there is not generated by us as neither our web installer nor our regular updater uses the TAR file. |
I wrote Ansible playbook for that. The location of this temp file made me think that it is part your installer process, yet I will check now to ensure this is correct assumption |
This is still an issue on Nextcloud 16.0.1. The instance was installed manually using the tar.gz file downloaded on the official website. The server is a Synology box running Apache 2.4 with PHP 7.2. |
Please don't respond to closed and stale issues. This issue is closed since 2017. There is a similar issue for newer versions #15681 or create a new issue. |
I am doing fresh automated install of NextCloud and each time it reports integrity check issue:
The trick is that the file does not exists and as name suggests it is probably something that existed during installation, so the bug is most likely in the order of operations as integrity should checked after all temp files are removed.
Rescan solves the issue
The text was updated successfully, but these errors were encountered: