RomanZ

Hi all, Could you please run a command in console and send me and output? ls | iconv --from utf8I suspect that you might have incorrectly encoded filenames in your foler. Please send output to syncapp@bittorrent.com and refer this topic and my name in message subject. Thanks!

@Untoter Known issue. Will be fixed soon.

@adam1v Why can't you add btsync user to your ad group? Also, you can adjust umask for btsync user to make all files synced to NAS available for RW access to all users, if you want. For any of the about you'll need SSH access to your NAS. I'm really not sure if it is possible to make from UI.

@Syncuser2014 If you enable the app preference "Allow Copy key" - every key can be copied in 2 clicks. First - the "..." button of the folder, second - "Copy xxxxx key", where xxxxx can be RW or RO.

@kidonthebeat It will work, but only for no more than for 49 customers. Currently Sync can't maintain more than 50 simultaneous peers. We are planning business edition of Sync which will be able to work with more peers. Also, I tested it in my lab - every time I generate a link - it is different, with different one-time key. When inspecting link - please pay attention co "i=..." parameter. It is actually the one-time key. The rest of params will be the same. See here for more details about what is included in link.

@adam1v On your the left screenshot looks more like windows permissions while right one more like Linux ones. Linux permissions work completely different - you can't make multiple users as owners - but you can put them in the same group and allow this group to RW the file.

@colinabroad Well, in 1.4 you still can see which files are yet to be transferred: make sure that "peers" column is shown, click it, and then click some peer with up / down arrow - it should unwrap the list of files to be transferred.

@mogarick We want to support WD new firmware in future, but I cannot claim any plans / ETAs due to project status (beta). Please stay tuned for the news.

@tjarra We are working to adopt Sync for iOS8.

@TiZ Debug logs. Give 3-5mins after issue happened - and collect it. Also provide a name of a file that was incorrectly overwritten.

@lisp Just to make sure I understand you correctly: 1) When you were using Sync 1.3, files with Korean symbols in filename were syncing to PC with no issues. 2) After you upgraded your PC and Android device to 1.4, files with Korean symbols no longer sync. Is this correct? If yes - I'll need your debug logs.

@wwlee Could you please: 1) pack your %programfiles%\BitTorrent Sync folder content 2) pack your %appdata%\BitTorrent Sync folder (just exclude sync.dat, sync.dat.old and settings.dat, settings.dat.old files as they contain your private information) and send to me? It looks like something went really wrong with your installation, and I'd like to see what exactly. Most likely full app cleanup and reinstall will help you, but I'd prefer to understand what happened.

@tenjaa It's more about the Sync logic than packaging. Regardless of the fact how Sync will be packaged - it still will run under some user, so all new files will be crated with this user as owner and with user's umask applied to permissions. The only one permission that is being synced for Linux machines is the permission to execute files.

@Spacemarine It is not a bug, rather configuration issue. For the computer which receives backup the backup key looks like read-only key with all the read-only properties. It means, that you may open the folder preferences and check the setting "Overwrite any changed file". In this case, your PC will request backed up file again if you change / delete it. Note, that it will work only if file still exist on your device producing backup data.

@adam1v As I mentioned in another thread - it is not bug. The fact that Sync does not copy owner and set of permissions is the design.

@nickluck I've got some updated info - the "0" value means "Do not cache peers". So setting to 0 should help you. And - yes, this setting need to be applied to 3 of your laptops, otherwise other laptops will attempt to connect to your one (and succeed if IP did not change). Also, it is advised not to leave "peer_expiration_days" as zero forever and set it back to some positive value after you reset cache successfully.

@nickluck Thanks for explanation. Your issue happens due to fact that Sync remembers last peers it was syncing to, so it can approach them even without LAN discovery or contacting Tracker or DHT. There is no explicit control which can reset the cached list, though you can do the following: 1) Open the preferences -> advanced -> more options 2) Set the "peer_expiration_days" to 1 (don't set it to zero, zero means - never setting it to zero means - "do not cache") 3) Sync will forget about your remote peers after nearly one day since last contact.

@adam1v As to your permissions issue - it is the design. Permissions (and owning users as well) are not transferred by Sync. Sync runs under some user. When Sync receives new file - it creates a file with the user and user group which actually running the process as owner and sets permission according to umask.

@Memoria Could you please check and rate the quality of Korean localization of Sync for desktop (and for any of supported mobile platforms)? Is there any inconsistencies or maybe some of text differ from how it used to be in apps in Korean? Thanks!

@PacketMan It is rather simple. Treat it in next way: last release of a version is compatible to whole next major version. For example: 1.2.94 is compatible to whole 1.3, 1.3.109 is compatible to whole 1.4. No one guarantees that 1.2.94 is going to be compatible to 1.4.

@sdafgsdfg Try opening the folder, pushing dots menu, "Select", then tap checkbox button in upper right corner to select all, then tap "Clean". Is it something you are looking for?

@kidonthebeat Could you please elaborate what is the scenario of using many different links?

@liver This property is now a part of x.509 certificate. It can be set only once on any platform. If you want to change it - you need to reinstall with settings cleanup.

@dimazigel I suppose taking a look to this topic - it looks to be related (briefly: WD updated their firmware and now many apps including Sync are not compatible).

@questorfla The protocol to actually sync data did not change between 1.3 and 1.4 versions, so they should cooperate with no issues.The idea stays the same - as long some folder has the same secret (now it called "Key") - it will sync. There is no "Sync" button, but Sync keeps direct connection to other Sync instances and checks the tree hash against other tree hashes all the time (or once per 10 seconds if it is impossible to keep TCP connection). As soon as tree is changed, it starts merging it to find out what exactly has changed. If something is not working between your 1.4 and 1.3 - we can take a look into debug logs to see why is it not syncing. If you can't get log from 2 peers (as you say people are not interested a lot in Sync backup) - let's try to get at least one from your backup server.