"syncing: no connected device has the required version of this file"

If you wouldn’t mind, could you take the Syncthing binary from the latest dev build:

https://github.com/syncthing/syncthing/actions/runs/16075219364/artifacts/3466352886

And run:

syncthing debug database-file tnhbr-gxtuf TreeSizeFreeSetup.exe

and also

syncthing debug database-counts tnhbr-gxtuf

(You don’t need to upgrade your setup to this version, just downloading it and running it with those parameters should produce a couple of tables of information)

I ran the Syncthing from the highlighted zip file but got error.

D:\>syncthing debug database-file tnhbr-gxtuf TreeSizeFreeSetup.exe
syncthing: error: no such folder

D:\>syncthing debug database-counts tnhbr-gxtuf
syncthing: error: no such folder

You need to unpack the syncthing-amd64 zip file and run the Syncthing from there.

D:\syncthing-windows-amd64-v2.0.0-rc.22.dev.11.gff88430e>syncthing --home=c:\PortableApp\SyncTrayzorPortable-x64\data debug database-file tnhbr-gxtuf TreeSizeFreeSetup.exe
syncthing: error: no such folder

D:\syncthing-windows-amd64-v2.0.0-rc.22.dev.11.gff88430e>syncthing --home=c:\PortableApp\SyncTrayzorPortable-x64\data debug database-counts tnhbr-gxtuf
syncthing: error: no such folder

Same results whether I use --home flag or not.

Just to confirm, your regular setup is 2.0.0-rc.22?

I guess in that case it most likely means that the --home is not the path to where the database (index-v2) is stored. I don’t know how the portable thing is set up, sorry.

In the Web GUI, you can check your actual paths in Help → About → Paths. In this case, the one under “Database Location” should be what you need.

D:\syncthing-windows-amd64-v2.0.0-rc.22.dev.11.gff88430e>syncthing --home=c:\PortableApp\SyncTrayzorPortable-x64\data\syncthing debug database-file tnhbr-gxtuf TreeSizeFreeSetup.exe
DEVICE   TYPE  NAME                   SEQUENCE  DELETED  MODIFIED                      SIZE      FLAGS    VERSION                                BLOCKLIST
-local-  FILE  TreeSizeFreeSetup.exe  499       del      2025-07-04T11:52:36.2804841Z  0         -------  HZJYWFM:1751507473,OMKHRPB:1751629956  -nil-
J5WNYJ6  FILE  TreeSizeFreeSetup.exe  500       del      2025-07-04T11:52:36.2804841Z  0         -------  HZJYWFM:1751507473,OMKHRPB:1751629956  -nil-
23NHXGS  FILE  TreeSizeFreeSetup.exe  445       ---      2025-06-23T03:16:10.2804841Z  13832808  -nG----  HZJYWFM:1751507473                     7B4kLitF
JKX6ZDN  FILE  TreeSizeFreeSetup.exe  320       ---      2025-06-23T03:16:10.2804841Z  13832808  -------  JKX6ZDN:1750992570                     7B4kLitF

D:\syncthing-windows-amd64-v2.0.0-rc.22.dev.11.gff88430e>syncthing --home=c:\PortableApp\SyncTrayzorPortable-x64\data\syncthing debug database-counts tnhbr-gxtuf
DEVICE   TYPE       FLAGS    DELETED  COUNT  SIZE
-local-  FILE       -------  ---      0      0
-local-  FILE       -------  del      1      0
-local-  FILE       --G----  ---      44     1501977502
-local-  FILE       --G----  del      3      0
1 Like

Thank you, I understand now. Will hack on it.

The problem here is that there is a sync conflict between two versions of the file (scanned independently on two different devices). One of them wins, but the losing device is apparently not online to resolve it at the moment and the conflict remains. No problem so far.

Once the file is deleted, however, it is still in conflict with the old version from the offline device and now we resolve it differently because in a conflict between a deleted and a non-deleted file, the deleted file always loses.

This obviously results in incorrect behaviour in this case.

2 Likes
2 Likes

I don’t get why these files have conflicts. None of them were modified in any way on any devices after they were downloaded from the web.