Always same amount of "out of sync" items

Hi

I’m using Syncthing between a NAS Asustor where Syncthing is installed in a Docker container, and 2 smartphones.

  • I’m syncing only one side folderpairs, either from NAS to smartphone or reverse bot no 2 way sync.
  • One smartphone synchronize perfectly, and is “up to date”
  • one smartphone always is state " Out of Sync Items [33 items, ~21,5 KiB]", and starting sync again and again.

When clicking on link to get list of not synced items, list shows nothing ( empty list ).

On NAS, log is showing this:

2024-02-15 18:33:33 Established secure connection to MYSMARTPHONE at 172.17.0.3:47264-46.232.251.36:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-5TK36P8M1KM92GA900OQRGUNPM
2024-02-15 18:33:33 Device MYSMARTPHONE client is "syncthing v1.27.3" named "mysmartphone" at 172.17.0.3:47264-46.232.251.36:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-5TK36P8M1KM92GA900OQRGUNPM
2024-02-15 18:33:45 Connection from MYSMARTPHONE-DXDZQ5W-62ADEWF-3D7NJ54-OZBDTCR-2DAGPUA-NHYLV36-FDPZAAJ at 129.13.64.138:443 (relay-server) rejected: already connected to this device
2024-02-15 18:41:04 Lost primary connection to MYSMARTPHONE at 172.17.0.3:47264-46.232.251.36:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-5TK36P8M1KM92GA900OQRGUNPM: read timeout (0 remain)
2024-02-15 18:41:04 Connection to MYSMARTPHONE at 172.17.0.3:47264-46.232.251.36:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-5TK36P8M1KM92GA900OQRGUNPM closed: read timeout
2024-02-15 18:43:30 Established secure connection to MYSMARTPHONE at 172.17.0.3:47268-46.232.251.36:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-5TK38UNVBIUD8OLV1CKLSR1E9O
2024-02-15 18:43:30 Device MYSMARTPHONE client is "syncthing v1.27.3" named "mysmartphone" at 172.17.0.3:47268-46.232.251.36:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-5TK38UNVBIUD8OLV1CKLSR1E9O
2024-02-15 18:51:01 Lost primary connection to MYSMARTPHONE at 172.17.0.3:47268-46.232.251.36:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-5TK38UNVBIUD8OLV1CKLSR1E9O: read timeout (0 remain)
2024-02-15 18:51:01 Connection to MYSMARTPHONE at 172.17.0.3:47268-46.232.251.36:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-5TK38UNVBIUD8OLV1CKLSR1E9O closed: read timeout
2024-02-15 18:53:35 Established secure connection to MYSMARTPHONE at 172.17.0.3:47272-46.232.251.36:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-5TK3B55PD47UI1O5BKRKQ6KV7C
2024-02-15 18:53:35 Device MYSMARTPHONE client is "syncthing v1.27.3" named "mysmartphone" at 172.17.0.3:47272-46.232.251.36:22067/relay-client/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P50-5TK3B55PD47UI1O5BKRKQ6KV7C

I cannot locate any error or clue on smartphone side. I cannot also guess what folder is unsync : all folders are up to date on both sides.

Any idea how to solve that problem ?

Can you post screenshots of the Syncthing Web GUI from all devices? On the phone, you can access the Web GUI from the left slide-out menu.

Hi

Thanks for your answer.

In the meantime, I was able to isolate the share that was causing the problem: on the NAS side, I paused the shares dedicated to the smartphone one after the other.

When I came across the problematic share, the smartphone status changed to “up to date” (still on NAS side)

After unsuccessfully trying to modify a few settings on that share (“ignore permissions” on the NAS side) without making any difference, I ended up destroying the share on both the smartphone and NAS sides, then recreating it from the phone. The share synchronized immediately without a hitch.

I don’t remember the conditions under which I created this share, but I noted the following point: the creation of a share where an android 13/14 is involved must imperatively be done on the android side via the app interface (not via the web interface), otherwise you’ll have big problems with data access rights: it’s only when the share is created from the app interface that android displays what’s needed to grant access rights to the directory you intend to share.

If you’re creating a share on a remote server, you can imagine that you’ll be able to count on the new share being discovered on your android: you can indeed see the new share proposal appear on android, but only from the web interface… and if you create the share from this interface, you’re cooked.

This sounds like a bug or misconfiguration. The app should present you with a notification about adding a new folder. Is the app allowed to show notifications in the OS permission settings?

Yes notifications are enabled, I always have a notice about “syncthing is running”, or “disabled” if smartphone is not on wifi. This is currently what I want : I used wifi only, and filter on listed wifi names. I took also care about changing localisation permission from “only when app is used” to “always”, in order to get syncthing working again when back on wifi and not calling the app.

All sounds correct. Normally, the app should pop up new notifications every time you share a folder from another device.

hi

you are right: I checked that with a new share. How did I missed that all the time before ? no idea… :upside_down_face:

Now if you missed the notification, or closed it, you are still cooked. :smiley:

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.