Harold Feit

It's possible

You have to provide your own cloud with BitTorrent Sync. We don't have a copy of your files. Only you do.

You should be able to. At worst you have to close sync down before you do and restart after

Are you using the same build across all machines?

Did you purge the settings.dat file from your .sync folder?

Did you use full access secrets on both devices?

Are all of your devices running the same version when you get this error?

I can say for sure about your first question that you can adjust the archive's storage day count in preferences - advanced. the value is sync_trash_ttl and the value is in days. I'm PRETTY sure that you can just delete the files from the syncarchive folder and it won't break anything. If you want to test safely, move the files completely out of the archive folder to a folder that isn't part of the sync. Each individual computer's syncarchive folder is independent.

You've restarted sync on both devices since updating?

That type of setup is indeed safe, due to the fact that you're dealing with identical data. What will happen is that both devices will continue to index. As they index, they will exchange information on the files they've indexed. Those files will then be checked against each other and the one with the newer modified timestamp will be used.

Sync is either informed by the operating system of the device or it scans on its timed interval and updates that way. You need to do nothing.

Time for the seedbox to update if that is the actual version number of btsync that is on it. Downgrading your NAS is not likely to solve things and is not supported. There are major protocol differences between 1.2.x and 1.4.x

You can validate the architecture of it by using "uname -a" from the command shell.

Find and replace the btsync-core file with the btsync binary from our package.

btsync-gui is, as far as I'm aware, a separate 3rd-party application and not what you want to be replacing. Check your process manager (such as top or htop) for other btsync applications, once you find them, you can use that to find the correct location for the executable to replace.

What internet explorer versions are on your machines?

Across major versions, we have rarely done autoupdates because of compatibility breaking. 1.3.109 and 1.4.72 are the two current versions.

Not actually up to date unfortunately. Current is 1.3.109.

download the current package for your variant of linux from the download page, find the location where the btsync binary is located and replace it with your downloaded version.

The repositories for apt-get have not been updated (last I checked) so your debian system likely isn't using a 1.4 series version like the windows and rpi are, which is likely the cause of your issue.

What versions of Sync are on the three devices?

It means that machines using a common shared secret will cooperate in getting the files from each other in a distributed manner. With sync, if it's not in a shared secret that YOU have specified in your settings, it won't be transferred to OR from your devices.

You're limited by the slow point in the stream, usually the upload speed somewhere along the way. 500kbyte/sec upload on a non-local connection is actually fairly good.

That's fine as long as you leave the other discovery options enabled. This will just attempt to force you to use local communication when the computers are available locally.

You could try using predefined hosts specifying the internal IP with the matching listen port for the other machine if something is actively blocking the local peer discovery.