Helen

gerard, how are your computers connected - rw, ro, owner? what are these files? does Sync reports that is has something to upload/download? Currently sync 2.1.4 is the latest and is not available for autoupdate, only for manual download and install. To debug your case, please update all peers and submit logs from both peers to support. Please indicate which exactly folder is having the problem.

Hello, It shall disappear from the list in 7 days, but due to known bug it won't. will be fixed.

KonstantinMiha, There is support ticket opened, let's proceed there,

NicCo, You mean sharing nested folder as RO? This cannot be done - nested folder cannot be added as RO shares.

Sync already does that, since long ago, and adds .Conflict to filename This is something team is planning to do

Matheu, Looks like a connectivity problem. What are you devices? What is the network, how devices are connected to it? What Sync version you use? Here are the step to troubleshoot Otherwise, please send the logs to support

Well, must admit that it's pretty much sync's problem. Solution is found and implemented, now packages need to be recompiled and released, which will take some time. So far, please do add the line to config as advised above. Thanks.

NicCo, You mean share RO folder with other peers? Only Owner can share the folder, so sharing shall be initiated from folder owner peer. But if another peer connects to the mesh, RO peer will also be able to upload some *unchanged* files to the newbie

rbtsync, ok, the problem is? you launch Sync with config where you define speed limits. After that you launch Sync without config speed limit defined in not saved, right? Even though they now are using same storage. And you mean speed limit it no honored when you sync files, right? If yes, then you need to set "rate_limit_local_peer" to true, using this script python btsync_edit_settings_w4.py .sync/settings.dat set rate_limit_local_peers true//check that it's applied by python btsync_edit_settings_w4.py .sync/settings.dat get rate_limit_local_peers

1 - yes. this option forces RO peer to receive changed files from RW peer again. The link provided explains the behavior in details.

Davide, Sorry, not implemented yet. It's in backlog for future release though. Thank you!

rbtsync, And what is "make changes in the config from UI"? What exactly changes you make? I can think of the following possible cause: when you run ./btsync --nodaemon --webui.listen 0.0.0.0:8080, sync settings and db files are stored in .sync directory near btsync binary and these are used by Sync. When you run in config mode, settings and db files are stored in "storage_path" defined in config (if you actually define it there), so these are different settings

NicCo, 1) - yes if you have "Overwrite changed files" enabled for RO. Detailed about RO are here 2) possible, just make sure files remain exactly the same. To help Sync with that enable "Overwrite"

drego85, Can you please check one thing - is the problem relevant for 1.4 folders as well or only for 2.0 folders? In any case, sending logs to support team is welcomed.

azromarie, hate to say that, but yes - files deleted in that way skip the bin, and this cannot be undone, There are two ways to try to restore them: re-download them from other peers and/or backup source, if they happen to have the files. And to try data restore utilities and apps. I cannot guarantee success of any of these utilities though. We are considering to get rid of that option.

@all, indeed, alpine4k is not supported now. But developers are investigating this. I cannot promise anything now, but we hope that it can be done. Thanks.

zbigb69, no. You can just download it manually and install.

solution: add the following line into config in folder prefs: "overwrite_changes" : true,

Then you add C:\user\Documents\footscan\Settings/database/footscan to Sync on Windows and when connecting it in Sync on Linux, pick /home/user/footscan/Settings/database/footscan. Sync will rehash the files and compare hashes. The files whose hashes are different get re-sycned. be careful with syncing bd, especially if it's being actively used by an app.

As far as I understood, jgc1984 want s to sync some D:\Documents on PC1 with F:\Documents on PC2, correct? If yes, than here's the guide But Moe is right and one cannot share physically same folder by different instances of Sync.

Mikeman, For this case, we will see what we can do and report that it's synced. Thanks!

no, the problem is not in ports or connectivity. on NAS go to /usr/local/bittorrentsync/var (via ssh or sftp) open sync.conf and add "/usr/local/bittorrentsync/var" to "dir_whitelist" string. so that it looks like this save the changes Restart Sync

Daevski, That's right - if the files are changed on RO peer, they are later skipped by Sync and syncing of them will stop. RW peer will show these file as yet to be uploaded, while RO will say it's synced. This is by design. To avoid it just enable "Overwrite any changed files' option in Sync on RO side. And if a file there gets changed, it will be immediately re-synced from RW to match it. This is way easier than disconnecting the folder each time.

paparoux, diskio job in log means that this file is involved in some ...well... disk io job so the torrent will not be loaded for it till this job is done. won't connect file .... no diff - Sync cannot check or the files indeed doesn't have difference on two machines. Please update to 2.1.3 and submit logs to support team. Thank you !

Hello, yes, please send them to us. via the web form. Hope they are not too big to attach? Thank you! mention the topic forum and add that this is for Helen. Thank you.