Error: Folder path missing or Out of Sync

I have a Windows computer using v2.0.3 and an Android phone using v1.30.0. It was working fine, but suddenly since yesterday the sync stopped working. On the phone the error says “folder path missing” or “out of sync”. On the computer it says nothing. Here is the recent log in the computer:

2025-08-28 20:28:29 INF Exiting (log.pkg=syncthing)
2025-08-28 20:28:30 INF Saved log output (path=C:\Users\ganuo\AppData\Local\Syncthing\syncthing.log log.pkg=main)
2025-08-28 20:28:30 INF syncthing v2.0.3 "Hafnium Hornet" (go1.25.0 windows-amd64) builder@github.syncthing.net 2025-08-22 07:00:05 UTC (log.pkg=main)
2025-08-28 20:28:31 INF Calculated our device ID (device=KEIORUM-QFPRO5W-EBJDUJT-QSJNKAM-QYMRH27-CL7QW6M-DBFG2XV-APZXHQV log.pkg=syncthing)
2025-08-28 20:28:32 INF Measured hashing performance (perf="193.93 MB/s" log.pkg=syncthing)
2025-08-28 20:28:32 INF Overall rate limit in use (send="is unlimited" recv="is unlimited" log.pkg=connections)
2025-08-28 20:28:32 INF Relay listener starting (id=dynamic+https://relays.syncthing.net/endpoint log.pkg=connections)
2025-08-28 20:28:32 INF Using discovery mechanism (identity="global discovery server https://discovery-lookup.syncthing.net/v2/?noannounce" log.pkg=discover)
2025-08-28 20:28:32 INF Using discovery mechanism (identity="global discovery server https://discovery-announce-v4.syncthing.net/v2/?nolookup" log.pkg=discover)
2025-08-28 20:28:32 INF Using discovery mechanism (identity="global discovery server https://discovery-announce-v6.syncthing.net/v2/?nolookup" log.pkg=discover)
2025-08-28 20:28:32 INF Using discovery mechanism (identity="IPv4 local broadcast discovery on port 21027" log.pkg=discover)
2025-08-28 20:28:32 INF Using discovery mechanism (identity="IPv6 local multicast discovery on address [ff12::8384]:21027" log.pkg=discover)
2025-08-28 20:28:32 INF TCP listener starting (address="[::]:22000" log.pkg=connections)
2025-08-28 20:28:32 INF QUIC listener starting (address="[::]:22000" log.pkg=connections)
2025-08-28 20:28:32 INF GUI and API listening (address=127.0.0.1:8384 log.pkg=api)
2025-08-28 20:28:32 INF Access the GUI via the following URL: http://localhost:8384/ (log.pkg=api)
2025-08-28 20:28:32 INF Loaded configuration (name=OokerLaptop log.pkg=syncthing)
2025-08-28 20:28:32 INF Loaded peer device configuration (device=7AKM7QB name="Nhật — Vivo" address="[dynamic]" log.pkg=syncthing)
2025-08-28 20:28:32 INF Ready to synchronize (folder.label="Tất cả dữ liệu Quả Cầu" folder.id=yxqea-krdlp folder.type=sendreceive log.pkg=model)
2025-08-28 20:28:32 INF Folder changed state (folder=yxqea-krdlp state=scan-waiting log.pkg=model)
2025-08-28 20:28:32 INF Folder changed state (folder=yxqea-krdlp state=scanning log.pkg=model)
2025-08-28 20:28:42 INF Detected NAT type (uri=quic://0.0.0.0:22000 type="Full cone NAT" log.pkg=connections)
2025-08-28 20:28:42 INF Resolved external address (uri=quic://0.0.0.0:22000 address=quic://118.68.56.152:22074 via=stun.miwifi.com:3478 log.pkg=connections)
2025-08-28 20:28:45 INF Established secure connection (device=7AKM7QB connection.local="[::]:22000" connection.remote=27.2.137.159:40278 connection.type=quic-server connection.lan=false connection.crypto=TLS1.3-TLS_AES_128_GCM_SHA256 connection.prio=40 connection.id=62VU5AA6EBF72QU8FVCD9SLAVK log.pkg=connections)
2025-08-28 20:28:45 INF New device connection (device=7AKM7QB address=27.2.137.159:40278 remote.name=SM-J610F remote.client=syncthing remote.version=v1.30.0 log.pkg=model)
2025-08-28 20:28:52 INF New external port opened (protocol=TCP external="[21.97.212.33:43818]" local="[::]:22000" gateway=9137a101-8ccf-4d5b-8550-0386b9c0f37c/WANDevice/urn:upnp-org:serviceId:WANIPConn1/urn:schemas-upnp-org:service:WANIPConnection:1/http://192.168.100.1:5000/ctl/IPConn log.pkg=nat)
2025-08-28 20:28:52 INF Detected NAT services (count=1 log.pkg=nat)
2025-08-28 20:28:59 INF Joined relay (uri=relay://156.224.76.76:22067 log.pkg=relay/client)
2025-08-28 20:29:13 INF New external port opened (protocol=UDP external="[21.97.212.33:43818]" local=0.0.0.0:22000 gateway=9137a101-8ccf-4d5b-8550-0386b9c0f37c/WANDevice/urn:upnp-org:serviceId:WANIPConn1/urn:schemas-upnp-org:service:WANIPConnection:1/http://192.168.100.1:5000/ctl/IPConn log.pkg=nat)
2025-08-28 20:32:16 INF Lost device connection (kind=primary device=7AKM7QB connection="[::]:22000-27.2.137.159:40278/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P40-62VU5AA6EBF72QU8FVCD9SLAVK" error="reading length: timeout: no recent network activity" remaining=0 log.pkg=model)
2025-08-28 20:32:16 INF Connection closed (device=7AKM7QB connection="[::]:22000-27.2.137.159:40278/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256/WAN-P40-62VU5AA6EBF72QU8FVCD9SLAVK" error="reading length: timeout: no recent network activity" log.pkg=model)
2025-08-28 20:32:34 INF Established secure connection (device=7AKM7QB connection.local="[::]:22000" connection.remote=27.2.137.159:40278 connection.type=quic-server connection.lan=false connection.crypto=TLS1.3-TLS_AES_128_GCM_SHA256 connection.prio=40 connection.id=62VU6508QMMNEFVAPCK74UNT9S log.pkg=connections)
2025-08-28 20:32:34 INF New device connection (device=7AKM7QB address=27.2.137.159:40278 remote.name=SM-J610F remote.client=syncthing remote.version=v1.30.0 log.pkg=model)
2025-08-28 20:34:43 INF Folder changed state (folder=yxqea-krdlp state=idle log.pkg=model)
2025-08-28 20:34:43 INF Completed initial scan (folder.label="Tất cả dữ liệu Quả Cầu" folder.id=yxqea-krdlp folder.type=sendreceive log.pkg=model)
2025-08-28 20:34:43 INF Folder changed state (folder=yxqea-krdlp state=sync-waiting log.pkg=model)
2025-08-28 20:34:43 INF Folder changed state (folder=yxqea-krdlp state=sync-preparing log.pkg=model)
2025-08-28 20:34:48 INF Folder changed state (folder=yxqea-krdlp state=idle log.pkg=model)

Troubleshoot where the folder went, on the “folder path missing” side.

I get the idea, but I don’t know which specific folder is

On Android, please check the Web GUI. You can access it from the left slide-out menu.

1 Like

The path is

~/Tất cả dữ liệu Quả Cầu

While the correct path is:

storage/emulated/0/Tất cả dữ liệu Quả Cầu

Do you know why the change happened? I suppose any update shouldn’t change paths?

There was a change in the Android app to what ~ means a while back. You probably need to correct the folder path manually.

2 Likes

Exactly that :slight_smile:

Shouldn’t there be a notice for users? Also, why did the change should happen?

In the Web GUI, if you go to Actions → Settings, and then to Edit Folder Defaults, you can check the actual path that is meant by ~.

On the other hand, if you need to change your existing folder paths without removing and re-adding them from scratch, you can go to Actions → Advanced, and then under each specific folder change its path to a correct one.

If the folder is located on the internal storage, you can begin the path with /storage/emulated/0/ or /sdcard/ and then add the rest of the path. If it is on an SD card, then you will need to figure out the mount point of the card first. You may need an external file manager (e.g. Material Files from F-Droid) to do it.

2 Likes

I just got this error. The android app was a very recent install (within the last 10 days) so it’s odd the ~ definition change is only taking place now when from looking at other threads it changed a while ago.

I think there may be some incorrect behaviour in how the Android interface creates new folders

The gplay update was released just a few days ago, updating april’25 and older installs to a current version.

So previously ~ and / were the same, and now Syncthing decides that they are better to be different? Does this pertain to only the android app, or to the core?

It’s an Android thing. Don’t litigate it, move on.

1 Like

On a side note, on Android, the whole concept of ~ (or $HOME) doesn’t really exist, e.g. in the current versions of Android it does seem to default to / (which is useless, as the user has no rights to write there), but in the past, the variable was just empty. :wink:

1 Like

I meant Android in general, e.g. if you do adb shell echo $HOME, it will display /. :innocent:

2 Likes

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