Remote Device Stuck at "Syncing (99%, 225 MiB)" - Need Help

Support
1

I’m facing an issue where the remote device on my receiver has been stuck at “Syncing (99%, 225 MiB)” for more than a day. Both devices appear to communicate without any obvious problems, but the synchronization just won’t complete.

Here’s what I’ve tried so far:

  • Enabled debugging and searched for “Fail” or “Error” messages, but the logs are clean.
  • Stopped and restarted both Syncthing instances on both ends, using the --reset-deltas flag, but it didn’t resolve the issue.

What this issue affects: The sync process between two devices, where one remains stuck at 99%. It may be of interest to users experiencing similar partial synchronization problems.

What I’m hoping for:

  • Suggestions on what else to investigate or logs to check.
  • Insights into possible causes for this type of sync stall.

I’ve attached a few screenshots from both Sender and Receiver to help visualize what’s happening.

Thanks in advance for any help!

This is my Sender Image from Gyazo This is my Receiver (showing 99% from the Sender ubuntu Image from Gyazo This is what the details of this remote device is showing when I click it Image from Gyazo and this shows, well, nothing for some reason :frowning: when I click the link for Out of Sync Items Image from Gyazo

2

Here are a few more screenshots, from the receiver side, of all the folders related to the remote sender ubuntu. Image from Gyazo

Image from Gyazo

Image from Gyazo

Image from Gyazo

3

Can you show the same four folders’ information but from the sending side? Do the global and local state match or differ?

Also, what happens if you enable “Ignore Permissions” in the folder settings?

4

Unfortunately (or maybe fortunately, depending on how you look at it), I kept debugging this issue. While I couldn’t pinpoint the root cause, I did notice that deleting the immich-library folder allowed the sync to complete. I recreated the folder, but the issue persisted. After deleting it again and recreating it with a new name and ID, the problem went away. I then deleted the folder one last time, recreated it with the original name, and the issue didn’t return. I can’t reproduce it now—and honestly, I’m not sure I want to! :smile:

Thanks so much for taking the time to reply and help resolve this! It’s much appreciated.

1 Like