RomanZ

Thanks. Please communicate support to resolve an issue.

Hi hypercat, We plan to add extended attributes sync. Sorry, can't provide ETA for now.

Hi all, Syncing of extended attributes and file streams is on our roadmap.

dfrdman, What is the operating system? Could you please create a crash dump / core dump when app is hanging and send us for analysis? stanha, There is a known issue in BTSync: if files on local and remote peer has the same name which differs only in letters case, that files won’t be synced. The bug is fixed in upcoming release, but still exists in 1.2. I suspect you’ve stumbled upon this issue and by renaming file you just break the loop. acyclovir, Ethan, I guess you checked it with “Auto Sleep” option both on and off, right? If yes, it looks like BTSync fails to start the core in a background to do actual sync. Could you tap “Feedback” on your iPhone, agree to send the logs and let me know the ticket ID you get? I’d like to understand what is happening on your Android.

Hi Lukastt, BTSync uses 2 mechanisms to detect new files in sync folders: 1) system notifications. Very fast technique, but it is not fully reliable and hardly depends on OS notification mechanism. To a make sure that all changes are detected, there is a second way: 2) full folder rescan every 10 minutes (configurable) I suspect that BTSync does not receive OS notifications by some reason. Could you please check if your folders start syncing automatically within 10 minutes after you change something or you still need to restart?

igboo, 2.4 or newer. For ARM processors we don't have a build supporting glibc 2.3.

Thuantran, There is a known issue. Sync indexing stops when it encounters a folder which it can't process by some reason. For Windows drives it is a very common case due to fact that Windows creates "System Volume Information" folder which is only accessible for SYSTEM user, even not for admin. This issue is already fixed in upcoming release, for now I would advise avoid adding whole drive as a Sync folder.

Hi dms2013, Actually BTSync identifies other BTSync instances in local network over port 3838 using multicast requests. So devices in local network must be visible one to another even if tracker is inaccessible. Please make sure that the port is not blocked by local firewalls. All people who can't sync in China over internet, please check that: 1) Your computers can resolve DNS names t.usyncapp.com (tracker server) and r.usyncapp.com (relay server). First would be enough for computers to "see" each other (displayed in devices tab). If they can't be resolved - you can try to put actual IPs in your hosts file, 54.225.92.50, 54.225.196.38, 54.225.100.8 2) if you can actually connect to the tracker server. To accomplish this test you'll need a binary file which represents a legitimate request to the tracker server, send it to tracker server and see if response comes back. For Linux and Mac systems just get the file, put to some folder and run next command from command line: "cat udp_req.bin | nc -u t.usyncapp.com 3000" For Windows you'll need to download net cat utility first and run similar command: "type udp_req.bin | nc -u t.usyncapp.com 3000" If you can reach the tracker server, you are going to get response starting with "BSYNC..." like this If you can't - you'll get just nothing after your command. For the people who can't sync in local network: 1) Please check your firewall settings, if it you are confident that nothing is blocked - 2) I would appreciate collecting full debug logs from 2 peers that can't connect. Please provide logs for analysis and we'll try to find out what's happening. Looking forward for your test results.

igboo, It looks like your glibc version is too old. Try checking glibc version, we have a special build for linux with glibc 2.3 the oldest on our download site. To find the glibc version you can run "ldd --version" command or find your libc.so.* file and running it.

Hi dms2013, BTSync is still in beta phase so important decisions on its development are taken often. I don't want to set any false expectations for our users. My "consider" here would mean "we'd like to add it, but it is postponed due to more important things to do". Hope it makes things more clear.

Hi Sergio, There are numerous reasons why files might be not synced. The most common reasons are: - wrong permissions issue - file being locked by some other app - file name case was changed while renaming file (known bug). The most precisely it can be identified via debug log. Could you please collect debug log on both your peers and send me for analysis? Thanks.

Hi p1neapples, Couple ideas. - How many files do you have in general on your RPi device? Are they stored on SD card / external drive? My guess is: sync is going slowly when BTSync indexes folder (USB and Ethernet controller are sharing the same bus in RPi). It is also worth checking how long the file indexing takes in general - Also, when you get the slow sync issue, you can try to occupy the rest of the bandwidth between your RPi and PC. It might happen that issue is not in BTSync, but RPi can't transfer faster by some reason. - Finally, you can collect debug logs and send it to me for analysis. Speed issues are usually very complex to identify, but your logs might contain a hint if something is going wrong on your peers.

Hi Vitokhv, Please follow Sync support instructions to resolve your issue.

Hi Niko, Thanks for the dumps. I'll let you know analysis results.

Hi gents, Adding proxy support was moved due to other high-priority tasks, but is definitely on our roadmap. We can't provide precise ETA right now, sorry.

Hi idef1x, sirio81, This is a very basic support of subfolders sync (so I would avoid calling it "Nested folders support") and it is possible with several limitations: - Both parent folder and child folder must have RW permissions. - Both folders are treated as separate sync folder, so additional indexing will be done. - Other peers, that have parent secret WILL NOT seed the data to peers, owning only child folders. We'll update the FAQ.

Hi Thuantran, Isn't the drive which stops indexing a whole logical disk, like "E:\"?

superscott, Yes, it is possible and it is on our roadmap.

antol111, crazyk4952, Thank you for the graphs. Unfortunately, it is not that easy to find the root cause. We plan to make an extended debugging in BTSync targeted to debug speed issues, including saw-shaped traffic. I'll update the thread once the version is ready.

Hi Vitokhv, Could you please elaborate what exactly is not working? After you put the secret to your laptop and (probably) some other PC - do you see these computers in "Devices" tab?

Hi LeNouveau, There is no such option in UI on Android. It is highly not recommended to change BTSync config files manually even on rooted devices. We'll consider extending mobile devices folder options for future releases.

Hi johan.mach, Indeed, it might happen that mechanism determining if peers are in local network or not failed to detect it properly, in this case rate_limit_local_peers advanced setting will help. jrm, There is a speed limitation in the "Preferences" tab. You can limit maximum upload speed for BTSync. I'm attaching a screenshot as a sample.

igboo, Please do the following: -open console, run command "ulimit -c unlimited" -run btsync with "--nodaemon" switch. When btsync exits - please see the core dump file in btsync directory. Thanks!

igboo, Thanks. What about core dump file? Did you have a chance to notice it? If they are, they should be located either in folder where btsync binary stays, or in a hidden subfolder ".sync" which is created near binary. THanks.

Hi Igboo, The message "BitTorrent Sync forked to background, pid=xxxx" is okay. It just indicates that not BTSync is running and let you know the process ID. The fact that you can't find it in the process list later means that either process crashed or exited by some reason. Could you please verify if there are core dump files in btsync folder and provide a full debug log for analysis? Thanks!