RomanZ

Wupi, Nefarious, As @mojeda mentioned, it indeed looks like you are affected by "too many open files" issue, like in this thread. Please check if you have the "too many open files" message in your sync.log. If you do - the fix is coming and will be published soon. If no - I'll need your debug logs, configured for full output.

okibcn, The sum of the speed rates, not the one below, is effective. It is not very precise, though, especially when we are talking about transferring a bunch of small files.

Dpx, Our QA is a group of professionals doing a bunch of manual, automated, regression and other tests on BTSync builds before providing them to a public. Also, we are constantly improving our test coverage to ensure the quality of builds. Some bugs that manage to slip QA testing might be painful for our users, but are good fuel to improve our tests and avoid such situations in future. Please also remember, that BTSync is beta software and we are working hard to improve its reliability.

Hi btsyncid, In general, there are 2 kinds of secrets: Standard secret - generated by BTSync - consists of 33 alphanumeric symbols, where first one is a type of a secret, other 32 are actual 20-byte secret in Base32 encoding Custom secret - generated by user - consists of 40 or more symbols and is a valid base-64 encoded value of 30 or more bytes. We do not recommend using custom secrets since version 1.2, though they are still backward-supported.

koldKat, It does. It calculates hash of the file before actually syncing it. The difference of a size or mtime only a trigger to calc hash.

Olly, If your device runs iOS or WinPhone, it won't delete backed up photos even if you delete them on device. If you run Android - deleted photos will be cleaned up on back up PCs as well (which can be workarounded by telling BTSync to never delete files from SyncArchive).

Vladimir, BTSync supports FreeBSD starting from 8.3. 8.2 is not supported, so please upgrade your OS.

Martinjohn, The "Connection closed" error usually indicates that the issue happens on another peer. Can you share the logs from both machines?

Suntear, Could you please check if your PC has several active NICs (including virtual adapters)? BTSync subscribes for multicast packets to only one of interfaces, this might be the root cause.

all, We've managed to find the root cause. The issue is Linux-specific, we'll prepare the fixed build soon. For now you can roll back to 1.3.77 as temp workaround. Sorry for inconvenience.

all, We are aware of the "Too many open files" issue and working on resolution. Will update as soon as we have results. UPD. all, We've managed to find the root cause. The issue is Linux-specific, we'll prepare the fixed build soon. For now you can roll back to 1.3.77 as temp workaround. Sorry for inconvenience.

Hi all, Thanks for reporting. We are aware of this issue and looking for ways to resolve it.

0xdefec, It can't. ShareID is not a secret and cannot be used to access your shares. Your debug log is going to reveal IP addresses, files and folder names. You can throw it to my PM if you don't want to reveal it to public.

all, Thanks for reporting. We've found the root cause and it is already fixed.

all, Please share which devices do you use, which version of Android. Also - do you exit application or you just tick the chekcbox, close options, open - and it is gone?

JohnnyMac, Did you had a chance to get debug logs? They might reflect what was wrong with these files.

Suntear, myuchan, Thanks for reporting, i've reproduced issue in my lab easily. We are working to resolve it.

Hgt3345, For now it is only possible to write to BTSync's "home" directory on the SD card: "/Android/data/com.bittorrent.sync". We are looking for ways to provide ability to back up other folders on SD card.

justlikekevin, Device should not be necessary on LAN. It can connect over internet as well, if your iOS device has access to Internet by any means. Could you please describe if your Mint PC sees iOS device in the table as connected? The latest available version for desktop is 1.3.80 indeed, while it is 1.3.25 for iOS. The upgrade on Linux machine is rather straightforward: you need to upgrade the binary only.

Antimo, No, there is no need to keep the topic here if you submit feedback. Our support will do their best to help you resolving your issue. Only one instance (either topic on forum, or ticket in feedback) is enough.

Himselfv, There is certain limit of filename on windows (260 symbols). File encryption makes encrypted file name longer, so for now I would advise avoiding filenames longer than 120 symbols if your encrypted node is windows. Roman.

All, Could you please share couple of your debug logs so we can see which events trigger syndID read in your case? Thanks!

wupi, BTSync usually shows this error when it fails to write ".SyncID" file to the sync directory. I consider checking permissions of the user which runs btsync process: it should have full access to the sync folder.

Qusi, It depends on why your sync get stuck. Here is some of the most popular reasons: 1. Permissions. The user running btsync on your NAS has no enough permissions for some particular files / folders. 2. SyncIgnore. If some files are in SyncIgnore, the peer which wants to send them (and has no them in sync ignore) will show upload. 3. File locked by some other application. In 1.3 client you can click the "i" button in Devices tab (Windows and Mac only) to see which files are in upload / download queue, which might help you to locate problematic files. If all of the above does not help - please collect a debug log from both peers and send me for analysis.

Jack Nihil, 1.3.19, I presume? Can I get full debug logs from Android and some other peer that does not receive files?