RomanZ

@tehabe You told that you are using Mac and 2 android devices. Could you please check settings on your Android device? There is a setting, called "Auto-sleep" intended to save power of mobile device. It forces to unload the core of BTSync for a period of time (30 mins by default), during that time the device is not visible to other peers if BTSync runs in background. Please see if turning auto-sleep off resolves your issue.

@Bones, When BTSync says "Nothing transferred at the moment" - are you able to see another device in devices list?

@kisenberg No, BTSync does not sync file attributes from Windows to Linux. It just syncs the file body and applies umask as it set for the user running btsync process on Linux. There might be an issue to sync alt streams to Linux xattrs - it's worth checking. If this is the case, then the alt streams which are not possible to sync will be visible it sync queue on Windows desktop. The most often this error pops up when BTSync is unable to set mtime after it synced the file to Linux system. Technically the files were synced, but mtime has not been updated. And usually I see this error when users try to sync data not to a regular storage, but to SMB share. Check if the mtime of files which are mentioned in the logs is different from the originals.

@gmosquera You can find and clean up all files in %appdata%\BitTorrent Sync, it does not store information in any other folders. The log entries you shown ("Connection closed") just indicate that issue covers on another peer, so to find the root cause you need to see what is happening in the log at the same time on another peer. I suggest contacting our support with pair of logs from your peer, so we can help you with log analysis.

@benguild As BTSync stores 2 copies of trees when communicates to encrypted peers, my guess would be the same - the issue happens as syncignore is applied to encrypted filenames. Thanks for reporting, we'll try reproducing it in our lab.

@thavidu Thank you for your proposal. We plan to implement it in next major release, 1.4.

@aaronmk WebUI requests to set the password at the very first run. It is up to user to decide if it wants to make it secure or not.

@Neinstein, @Frederick888, Both files are good and produced by BitTorrent. The file on official download page contains one additional resource in its body which is responsible for displaying slightly different on-boarding screen (the initial screen after installation). No functional changes. @Moe They were intended to show in a short format. Thanks for the feedback. @JimmyTheSaint Got you, thanks for the feedback. I'll deliver it to new WebUI designers.

@Macwinuxit There is always a way to connect to your QNAP over SSH and simply run the binary on it! Just make sure that you choose a binary that fits your CPU.

@Michael Poss That sounds unusual. Folder re-adding is very likely to resolve your issue, but not reveal us its nature. If the issue still bothering you - could you please collect debug logs from 2 peers that suffer it and send to syncapp@bittorrent.com for analysis? Please refer to this forum topic. Thanks!

@zylorian I suggest posting your wish to feature requests forum to make sure it is not lost. As for issue #3 - we are preparing 1.4 release, which contains a numerous fixes towards sync speed as well as a tool to analyze possible speed issues. Once released many issues with speed are going to be addressed.

@keamas BTSync 1.3 uses both TCP and UDP for communications. The port 3000 is Tracker Server connection. Other ports seem to be other peers ports. They might look random by 2 reasons: 1) BTSync itself uses random port upon installation. This can be changed in config though. 2) Other instances of BTSync stay behind the NAT. NATs might change and randomise ports, so it depends on how the remote NAT is actioning.

@scegg It might happen to internal DNS cache of your DSL modems. Have you tried to flush the cache and force your dynamic DNS to be re-resolved after modem reconnection?

@cloakrune Also - which version do you use? 1.3 has log rotation built-in, so it should strip log file to 10 megs by default.

@benguild Thanks for reporting. We are aware of this issue and it is easily reproduced in our lab. We plan to fix it in next major release.

@tokejepsen I suggest contacting our support at syncapp@bittorrent.com so we can assist you. Please mention this forum topic in message body.

@negguy The files transferred are going to stay in "BTSync" application. To open them in any other app - you need to open BTSync and explicilty direct it to "Open in..." and choose some app, then it will be saved in another app as well. This is the limitation of iOS itself.

@benplumley Okay, what about initial issue? Are files re-indexed 20 minutes or it is done in a prompt manner now?

@jachin You can delete this file, and it will definitely reset the password. Though, it will remove a bunch of settings as well.

@Zian, This message only means what it says: BTSync did not manage to read file because OS returned code which indicates "file not found". Do you experience some functional issues with BTSync? Are there some files it can't sync?

@HobbledGrubs It is very unlikely that BTSync corrupts that file. Every file is split to chunks, and after every chunk transmission BTSync calculates its hash and compares it to expected value.

@natebluehooves Currently BTSync has not ability to choose which network interface to use for connection. It will choose some interface provided by OS. I would advise to have only preferred interface on.

@queltos Proposed change is going to kill the usability for people who use btsync for NASes and install it via packages without any usage of SSA. It is bad that BTSync does not have an option to bind WebUI to only selected NIC, which is necessary for security-aware people - which is a good point for Feature Request forum.

Please see starting post here. We are working on documentation, so it will be available soon.

Please feel free to use build 1.3.106. Change log: - Fixed issue with inability to type in path manually in WebUI - Indexing is shown in WebUI when BTSync indexes files - Overwrite checkbox brought back for RO secrets in WebUI - Fixed issue with "#" symbol in the folder picker in WebUI - Fixed issue with encrypted secret not displayed in WebUI - Fixed issue with short / long path shown in WebUI - Fixed LAN discovery issue when many folders and files are added to sync dirs - Fixed continual indexing issue in certain cases - Minor cosmetic fixes Previous build change log.