sergey@bt

Employees
  • Posts

    86
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by sergey@bt

  1. Can you please send us debug log from both computers? Here are instructions how to collect it:
  2. Please try version 1.0.132. It should be already fixed there.
  3. Can you please send us debug log from read only computer? Here are instructions how to collect it: .
  4. What is your Linux version/arch? Do you see any more messages in log when you create debug.txt with FFFF? Do you use any config file for btsync?
  5. Currently in read only mode Sync does not overwrite files if they are modified locally. We are planning to add an option to force overwrite local changes. Can you please make sure that all files are really the same? You may try to sync with full access secret first, then re-add folder with read only secret.
  6. You may want to enable debug log to get more visibility about what's going on. Here are instructions how to enable it:
  7. Unfortunately re-adding folder will not help here. It should be fixed when all clients are updated to 1.0.130. We are planning to enable auto-update in a day or two. If you need it sooner, you may try the following workaround (but please test it locally first): 1. Install 1.0.116 (1.0.130 will not allow such trick), preferably on Mac or Linux - since initially your issue was caused by bug in Windows version. 2. Sync it with your folder with full access secret 3. Shutdown Sync and disconnect computer from network 4. Set time to 2015 5. Run Sync and remove selected files, make sure Sync sees that files are removed (files counter in UI) 6. Shutdown Sync and return time back 7. Connect network and start Sync again
  8. Can you please try the following: 1. Install 1.0.130 on all computers (if not yet done) 2. Remove shared folder on both computers from BTSync WebUI 3. Add folder on full-access computer 4. Add folder on read-only computer Previous build could save incorrect information in cache. Re-adding folder will rebuild cache.
  9. There are 3 points of contact with BitTorrent infrastructure: tracker, relay, check for update service (listed above HTTP request). If you don't use any of it - we will not get any information about you. As for brute force - a lot of things in cryptography is based on a fact that there is no other way to decrypt data besides brute force attack (e.g. you can not recover private key from public). We believe 160 bit random secret is strong enough here.
  10. Do you remember any file names which were bouncing between hosts? It would be good to grep by their names. You can send us results of the grep to syncapp@bittorrent.com.
  11. What version of OSX are you using? We will try to reproduce it in our lab.
  12. BTSync uses FSEvents API to get file notifications on OSX. Additionally BTSync does rescan of the shared folder once in 10 minutes. So if it you see file updates only in 10-15 minutes, it means file notifications do not work for you. Can you please try the following: 1. Make sure fseventsd process is running (this is a system process responsible for file system logging) 2. Try to add any other folder (e.g. ~/btsync) and check if it works. We saw few cases when fseventsd stopped to send events for particular folders. 3. Try to reboot your Mac.
  13. What version of Sync do you use? BTSync creates file .SyncID in each shared folder which is used to check that folder is properly mounted. If .SyncID becomes inaccessible, BTSync should stop processing any events for this folder.
  14. Could you please send us debug log from your Windows machine? Here are instructions how to collect it:
  15. You need to make sure btsync is able to communicate with Internet using UDP, not just your Linux VPS where you run VPN. You may try to analyze network traffic to port 3000 (which is our tracker port). btsync on your Windows machine should send and receive UDP packets to/from this port. BTW how do you route your Internet traffic through VPS? Do you run NAT or proxy on VPS? btsync does not support proxy.
  16. As a first step can you please check if BTSync is able to send and receive UDP packets via your VPN channel? If you have any shared folder, BTSync should send UDP packets to tracker and it should be able to receive reply. If you enable debug log, it should be visible there. Also you can just monitor BTSync port with some network analyzer (Wireshark for Windows).
  17. Did you put btsync executable into shared folder? Please move it out. By default on Linux btsync creates .sync folder with metadata in the same folder where executable is located. If you put .sync folder into btsync shared folder, it may create infinite loop.
  18. In current version zombie records (information about deleted files) are not removed automatically. We are planning to implement configurable time to live for them.
  19. It looks like you are trying to use one-time secret on more than one machine. One-time secret can be used only once. If you enter it again on another machine, it will never be resolved. This crash has been fixed in version 1.0.125 : http://syncapp.bittorrent.com/1.0.125/BTSync.exe It's still a test build, but we are planning to release it soon.
  20. If you don't set port manually, it's assigned by operation system. However BTSync remembers the port it gets the first time in config file and uses it after restart. When you changed the port manually, BTSync recreated UDP socket which is used for all communication. Did it resolve the problem with sleep? Did you try to restart your Mac?
  21. If you saw a case when you was not able to delete a file (file was restored back from another machine), can you please try version 1.0.125 from here: http://syncapp.bittorrent.com/1.0.125/ . It's still a test build, but we are planning to release it to all very soon.
  22. Could you please try this build: http://syncapp.bittorrent.com/1.0.125/BTSync.exe . Please remove shared folders from BTSync first and add them again after upgrade, since previous version could save incorrect state in cache. 1.0.125 is still a a test build, but we are planning to release update to all soon.
  23. This error means BTSync is not able to decrypt a message received from another peer. Do you run BTSync on Windows? Could you please try the following build: http://syncapp.bittorrent.com/1.0.125/BTSync.exe