RomanZ

toobs, The first thing I suggest checking is local firewall / security software. Make sure that UDP ports 3000 and 3838 are open, or for the clean test - just disable security software and see if issue is gone. If it does not help - i'll appreciate debug logs from both peers.

No one ever investigated it and I see no point doing that: the time going forward is a requirement for app to be running smoothly. It can show you which of your devices has incorrect time zone set. As I told above: - current solution is setting correct timezones, including correct DLS time setting. - we'll see what can be done to make it easier for user.

DesignMongrel, If you renamed the folder that was added to BTSync - you can either rename it back, or just remove in BTSync from UI then add a new folder with the same secret. It won't re-sync files if they were not changed.

Itcrowd, Sorry, I was not precise. Please try to make this folder on your external SD card, it should start working. Android 4.4 should let BTSync read/write data to "/Android/data/com.bittorrent.sync" on ExtSD with no issues.

guigolum, This is a known issue that indexing can freeze once it encounters permissions restriction in 1.2 client. It was fixed in 1.3.

hawibtsync, 1.2.82 is not compatible to 1.3. 1.3 introduces 2 major changes - TCP connection and syncing alternative streams and extended attributes. Both are not supported by 1.2.81, while should work fine with 1.2.91/92.

I'm an admin, so you can't. No probs, "thanks" is enough for me

Stanha, Please correct me if I misunderstand you: 1) Your RO node does not display any folders 2) it is not mentioned in RW logs in any manner. What happened "today"? Is it bound to the upgrade to 1.3 or you keep 1.2 version? Thanks.

kaldown, Glad to hear now it is solved!

cavy, It wants to access your account to get ability to send mails for 2 cases: 1) sharing secrets 2) sending feedback. Both are initiated by you, app does not send it automatically.

kaldown, I'm a bit suspicious about your first post: YAKT on PC is a timezone for Yakutsk, while Yekaterinburg has different timezone. Did you try to set automatic timezone configuration for iPad? If that was a typo and both devices are in the same timezone, lets try to collect debug logs and see what is the time difference indicated there. Thanks! Our development power is limited. But we have an API, so you might be first person making BTSync port for FreeBSD

Actually BTSync supports servers only starting from 2008 and newer, which was true for 1.2.xx builds as well. Technically we cannot guarantee that 1.2.91 works on 2003 server. kevinsky25, unsignedint, Note - Linux has a limitation for xattr to 4kb, while Mac is capable of storing much more data. This might be a reason why some xattrs can't be synced. kamborio, All your 10 PCs are in the same subnet?

cloudbitsync, Thanks for reporting, we'll take a look why is it happening.

Hi people, We know the root cause of the issue and are preparing the fix, will be available soon. wimbit, Just out of curiosity - your problem also happens on Samsung device or you have different hardware?

JimmyTheSaint, Did you have a chance to grab any logs / core dumps? Could you also please share more info on what kind of damage happened: newer files replaced with older or something else? Thanks!

Moe, It's on our roadmap. That's not true. I'm joining GreatMarko here, with some comments: it might make the "dumping ground" feeling because of feature demand and development ability not matching. Wishlist is huge now, around 1000 posts now. If even only 30% of them are unique features, it would be 300 features to implement - while release can have only several new features. I can reassure you that BT is constantly monitoring what is happening in Wishlist. tenjaa, Means BTSync scans folder with better algorithms. It still rescans them with every 10 minutes (or whatever time you configure), but 1.3 should be more gentle with sleeping HDDs and won't awake them until rescan happens.

kaldown, BTSync compares all time values in GMT, which means that it uses your locale settings to convert local time to GMT. So, even if your time is precise, a mistake in timezone may result in the error you see on your FreeBSD box.

Baci, Actually it depends on the amount of files smaller files are synced several in a row, while if sync starts big file sync - it won't touch others.

Dear all, I’m happy to announce the BitTorrent Sync 1.3 public release. Changes affected all supported platforms, plus we are proud to introduce support for a new platform: Windows Phone. Detailed change list: Desktop changes Support TCP connectivity between peers, tracker and relay (work when UDP is not available) Greatly reduced parasite traffic when between peers, tracker and during LAN search Improved behaviour with case-insensitive file systems (rename correctly) Extended attributes (OS X) and file streams (Windows) support Improved getting started assistant Sync notifications redesigned New advanced option: external (NAT) port can be configured Optimized folder indexing Added log rotation Fixed issue with permissions transfer on Linux and Mac during initial scan Fixed issue with sync getting stuck after folder removal Fixed issue when deleted files get restored after peer comes online Fixed issue when new version not checked on Linux and FreeBSD Fixed replacing invalid chars with "_" after sync Fixed sync stuck issue due to case-sensitive rename Fixed indexing hang when unable to access folder due to permissions Fixed sync hang due to network change until app restart Fixed Linux executable attribute loss when file modified on Windows PC Fixed app crash when entering invalid secret Added log rotation value in Advanced preferences Fixed several issues with freeze on Mac Fixed missing notifications Fixed issue with updates on Linux Added tooltips in Devices tab on Windows Fixed occasional app crashes Fixed stream appearing as file.com.apple.metadata after updating 1.2.91. Fixed issue with executable flag dropped after merging changes from win client to linux client Fixed issue with merging files tree Fixed issue with file moved to .SyncArchive after renaming (change case of letter). Fixed app hang when trying close app. Fixed check-for-updates issue on Mac Fix for Linux sync issue Fix for the crash on encrypted node Cosmetic fixes and changes UI improvements Android-specific changes: Fixed issue with app crash on switch from wifi to 3G Fixed crash on first run and help on Android 2.2 Removed mobile-to-mobile share tab Fixed issue with auto-sleep Fixed issue with QR recognition Added ability to cancel selective sync files Fixed issue with cellular data usage Android 4.4 ExtSD limited to OS designated folder Cosmetic fixes and changes iOS-specific changes: UI redesign Add possibility to share your sync folders via email, QR code or other apps from folder preferences bar Improved Auto-sleep and other battery saving options Optimized mobile data usage Made "Open in" option available while tap and holding Added filters in folder view Other fixes and improvements You can get Sync for all the platforms here.

klytus, Glad to hear that it is working for you now. That's rather strange. The storage contains a DB with all the info regarding folders and it should not be purged before every start of btsync. Could you please describe what BTSync is doing and what is happening if you do not clean up storage dir? Thanks!

YoBi, Most likely you are facing permissions issue on your Synology NAS. Please check which user is running your btsync process and make sure that it has RW access to the problematic folder. If it does not help - please try collecting debug logs from both peers and send me for analysis.

Hi Jimmy, When BTSync client is running on Android, it receives OS system notifications on file changes and is expected to sync them immediately (i.e. within 10-20 seconds). When BTSync "sleeps" it is not going to get any system notifications as the core is actually down and not working. It is going to rescan the sync folders once per 30 minutes and if any changes are found on Android (or any remote peers) - sync them. Once sync is complete and no traffic is flowing, it will sleep again for another 30 minutes. Please let me know if your behavior is different from described.

stanha, Just one little comment for the content you copied to your site: this is true for 1.2.82-1.2.91 versions of BTSync. It was slightly different in 1.1 and might change in future.

Cerebrus97, Please see TimCinel's response above on how to limit traffic to LAN only. When you disable tracker, DHT and relay server the only thing BTSync needs in Internet is update server which it contacts to check updates. Note, that if you have just only peer in LAN which contacts outside world and there would be another peer with same secret - it will let all other peers in LAN know the location of outer peer and they will connect outside.

Hi pii77, There are might be 2 straightforward reasons on why these files are not synced: 1) files are added to syncignore. Easy to check. 2) files were once removed on RO peer and BTSync remembered not to sync them anymore. Can be also checked easily: just open a sync folder properties and check a checkbox "Restore files to original if changed". If both are not your case - my proposal would be to collect full debug logs and send me for analysis.