Nextcloud version (eg, 20.0.5):
Operating system and version (eg, Ubuntu 20.04):
Apache or nginx version (eg, Apache 2.4.25):
PHP version (eg, 7.4):
The issue you are facing:
Error message stating
Conflicting versions of <filename> on some files that have been updated on another computer.
Is this the first time you’ve seen this error? (Y/N): N
It happens daily
Steps to replicate it:
- Two separate Windows client machines, NextCloud client 3.4.1.
- One computer is used and after files are updated the computer is shut down. (Daily)
- Second computer is used, and some files are edited and saved. Files are never left open when switching between computers.
- Booting up and logging in to first computer will receive the error message:
Conflicting versions of <filename>
- The conflict dialog shows that the Server file is both newer and a different size.
Why is a newer file listed as conflict? Isn’t that an indication of an updated file that needs to overwrite the older local file? Why must I do this manually each morning?
The output of your config.php file in
/path/to/nextcloud (make sure you remove any identifiable information!):
<?php $CONFIG = array ( 'instanceid' => 'instancidsucks', 'passwordsalt' => 'salty', 'secret' => 'secret', 'trusted_domains' => array ( 0 => 'yep.no', ), 'datadirectory' => '/var/www/nextcloud/data', 'dbtype' => 'mysql', 'version' => '188.8.131.52', 'overwrite.cli.url' => 'https://yep.no/nextcloud', 'dbname' => 'nextcloud', 'dbhost' => 'localhost', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'oc_user', 'dbpassword' => 'dbpassword', 'default_phone_region' => 'US', 'installed' => true, 'mail_from_address' => 'mail', 'mail_smtpmode' => 'smtp', 'mail_sendmailmode' => 'smtp', 'mail_domain' => 'google.com', 'mail_smtpauthtype' => 'LOGIN', 'mail_smtpauth' => 1, 'mail_smtphost' => 'google.com', 'mail_smtpport' => '443', 'mail_smtpname' => 'firstname.lastname@example.org', 'mail_smtppassword' => 'passwordsucks', 'mail_smtpsecure' => 'tls', 'maintenance' => false, 'theme' => '', 'loglevel' => 2, 'updater.release.channel' => 'stable', );
I’m leaving out a lot of the stuff that appears to be related to Server as this appears to be a client side issue. Please let me know if that is still required.
As stated above, it seems NextCloud is mislabeling updated files as conflicting.