Remirus

Members
  • Posts

    311
  • Joined

  • Last visited

Everything posted by Remirus

  1. Sync relies on UTC time. You need to have correct both time and time zone on all devices. If you have 5:00 UTC+01 and 5:00 UTC+00 you will have 1 hour time difference between devices.
  2. We have builds for WD EX2Ultra. If anyone wants to try it please send a personal message or submit a request there and mention your NAS model.
  3. According to the logs it happened because of old bug which appeared in 2.2.1 version. It was fixed in 2.2.5 so it shouldn't happen again. However, if it is was caught in 2.2.1 version before the fix, it is necessary to update modification time of the file on which Sync stooped synchronization. In the logs there will "failed to verify signature" message with the file name.
  4. jmensa, if you launch Sync on Linux, FreeBSD, NAS or Windows with WebUI you won't see "Open Archive" option, because it requires integration with OS. So you can open your shared folder in the file manager then find ".sync" folder. "Archive" folder is locate inside it. ".sync" folder is usually hidden on all OSes.
  5. In 2.3.7 version developers removed that string. So now Sync doesn't flood logs with that any more.
  6. jdrch, usually Sync checks if another instance is running. So if you proceed to update Sync while it is running, Sync will try to close the running process and install the update. However, if you have 2.3.0-2.3.3 version it is strongly recommended to backup storage folder(%appdata%\BitTorrent Sync Service) before the update and close Sync only after all folders are loaded, because those versions have a bug when Sync couldn't save information about folders.
  7. Mostarac, if you want to run PS games - that question is beyond Sync. Playstation is not officially supported. But I know that you can install linux there and try to synchronize files with other peers. However, if I remember correctly, it is not allowed to run a game on the Playstation if Linux is installed.
  8. Jaroslav, unfortunately I couldn't reproduce it. I've got the latest Debian Jessie iso for i386, installed Debian with some DE and added Sync. Then after reboot Sync starts correctly. Maybe you've tried to enable autostart under several users? Do you have another scripts to start Sync automatically? Or maybe some program causes Sync to start again?
  9. schpongo, we received your ticket. Let's continue our discussion in our support system.
  10. tufkal, you need to have read-write or read-only (not encrypted read-only key). Using it you can add the folder and receive unencrypted files from encrypted peers. But you need at least one encrypted peer working with launched Sync. If you just copy files from it's hard drive to your computer you won't be able to decrypt your files.
  11. Jaroslav, does your system use systemd or sysvinit/upstart? If you have systemd did you try to enable automatic run using this command: sudo systemctl enable btsync If you have sysvinit or upstart there is no such a feature and you need to write a script to launch Sync after system starts.
  12. schpongo, using Sync you can set read-write permissions on the laptop and read-only permissions on the phone. Then when you delete/modify a file on the laptop - it is deleted from/modified on the phone. However, Sync shouldn't restore deleted files. Unless you have file system permissions issue. Do you have some third peer? Maybe when you delete files from the laptop, Sync tries to delete it on the third peer, but files are not deleted (access denied). Then Sync discovers that file "appeared" in the folder and restores it. There can be something else. You can send feedback message from your laptop, mention this topic and agree to send logs.
  13. Yes, you need to do that on all peers. And if you have several folder, you need to to add it for each folder (because IgnoreList is different for each folder).
  14. vi10, you can add this string into IgnoreList: *.lnk It's better to do that on all peers, because if you ignore it only on one peer and you have other two peers they will synchronize shortcuts with each other, but the peer where you ignored it won't synchronize shortcuts.
  15. Megalith, thank you for clarification. Then we certainly know about it and that bug will be fixed in future. now as workaround you can save your files on the internal memory (I know that it might be inconvenient) or save files inside Sync's sandbox folder on SD card: path_to_SD_card/Android/data/com.bittorrent.sync/files
  16. Megalith, it can be related to Selective Sync. First do you have read-write or read-only folder on the Android peer? And does the folder located on SD card? If yes, we probably know about it. But files should remain on your device, they should only be "unsynced" in the Sync.
  17. jammin, did you choose correct folder location? Sync tries to avoid conflicts when you add a folder via link or reconnect it and suggest another folder name. Do you have "(1)" in the name? If yes, you need to disconnect the folder and connect it again. If everything is correct we need more details about your case. You can see which files Sync is transferring in the peer list(take a screenshot with names) then close Sync and show screenshot from both peers showing modification time. If Sync only writes that certain files should be transferred but there are actually no transfers it is normal behaviour, because it tries to send files to another peer, but other peer tell that files are the same so Sync won't transfer them.
  18. chicagonyc, we received your ticket with logs. Let's continue our discussion in the support system.
  19. pjmsullivan, thank you for reporting about it. The fix will be included in future versions.
  20. Bgregster, thank you for clarification. For 300-400KB/s Sync should download it for 29-38 hours if peers don't disconnect from each other, for 200KB/s it is 58 hours. Probably UI doesn't update remaining time so fast and probably the speed is different or peers disconnect from each other.
  21. pjmsullivan, we have a special build with IPv6 fix. I will send you it in PM. Please tell if it helps you.
  22. ecotec, you can edit config file: /etc/btsync/config.json There you need to replace 127.0.0.1:8888 by 0.0.0.0:8888, instead of 8888 you can specify another port. //before place: "listen" : "127.0.0.1:8888" //after replace: "listen" : "0.0.0.0:8888" The current value is set for certain purpose: no one will access WebUI unless you enable it.
  23. sahendrickson, there are many 2.1-2.2 versions. Here is the link for all published builds.
  24. Bgregster, it means that Sync stopped transferring data, synchronization cycle is complete. It doesn't mean that all files really have been transferred. Peers might disconnect from each other (or lose connection for a while), some files can be busy by another process so Sync doesn't touch files for some time and there can be another reasons. What is the size of the shared folder? Is it about 500Gb or more? Or just 6Gb? Maybe Sync will transfer it with better speed and you don't need to wait 5 days.
  25. fefrie, default IgnoreLists are almost the same, but for 2.x versions there are additional strings to ignore certain files. You just need to add a new string and place file or folder name you want to ignore. Here is an example: (starting from two last strings:) .@__thumb ._* Ignored-folder [Sample] Text under "#" symbol are comments. They were added to make it easier for you to organize ignored folders. But logic is the same and you can place new strings in any "section".