I’m using Nextcloud client version 3.16.2 in my Ubuntu 14 destktop. The client connects to a Nextclound instance running on raspberry pi 4. I have a synched folder in my desktop, there are many files I’ve updated. Some files were edited last week and I’m sure I have edited the files. After I noticed the client was not running, I’ve started it normally, but for my surprise, the files were replaced with the files (outdated version) from remote server. It seems the client ignored the new local file versions and just replaced it. What I missing here?
That sounds bad. Did you reindex the filecache table on the server between the syncs?
If a different client changed something on the files on the server side (even if it is just the last modification date), the client should then create conflict files.
Is it possible to reproduce the problem (stop client, change files and then start again)?
Does not exist. If you have Ubuntu 14:04 it is EOL since more then 5 years.
For sure you will have a backup of your replaced data. After all, every responsible Linux user creates regular backups. Nextcloud is not a substitute for backups. Restore it.
Ubuntu 24. I know Nextcloud is not backup, and now I know, perhaps, the client or Nextcloud itself it is not realiable. I’m not sure about that, I’s still testing to make sure I have uninstall and try another solution. Thanks.
Good advice. I will create another dockerized Nextcloud instance and test. I have two smartphones and a couple of hosts using Nextcloud as cloud solution. That is is the first time in three years I faced an issue. Maybe I have misconfigured the client.
I run a test today and the same issue showed up. So, I tried to run the Nextcloud on terminal and I got the following:
~/Programas/AppImages/Nextcloud-3.16.2-x86_64.AppImage
nextcloud.gui.application: Migrating old config from "/home/eduardo/.local/share/Nextcloud" to "/home/eduardo/.config/Nextcloud"
nextcloud.gui.application: Failed to move the old config directory to its new location ( "/home/eduardo/.local/share/Nextcloud" to "/home/eduardo/.config/Nextcloud" )
nextcloud.gui.application: Will move the individual files QList("Documentos_Nextcloud_obsidian-serpro-vault_sync.log", "EnvioAutomatico_sync.log")
nextcloud.gui.application: Fallback move of "Documentos_Nextcloud_obsidian-serpro-vault_sync.log" also failed
nextcloud.gui.application: Fallback move of "EnvioAutomatico_sync.log" also failed
Was that the same for the initial problem. Just in case the sync database on the client side, if you start from scratch, the client will probably start from 0 and take the server as master.