• Content Count

  • Joined

  • Last visited

Everything posted by Alex.

  1. @Steerider Could you please go to %LOCALAPPDATA%\Temp and check for btsyncsvc_*.log files? Which version of Windows do you use? Do you use any antivirus? Could you please try to install service manually using the following command? cd "%APPDATA%\Resilio Sync" ; "Resilio Sync.exe" /svcinstall -a -u %username% %password%
  2. @edudroidfc login to the jail and go to "/usr/local/bin" and replace rslsync binary also I wrote a letter to the maintener of the Sync's FreeBSD port. hope he will include this build to the port.
  3. @asdf123123 please install this version it will fix the issue with kmduseritems, resourcefork and kmdfindercomment You can uncomment these lines after installation.
  4. @muchogrande please install the following build on all OSX systems
  5. @psychjohn Could you please upgrade Sync to the latest version and gather logs from several peers including Synology? Also please check /var/log/messages on Synology for 'oom-killer', 'oom_kill_process', 'resilio' and similar
  6. @edudroidfc Yes! Just install this build
  7. @Hans# @fink I think self signed SSL certificate will solve your issue.
  8. @nmkaufman
  9. @devinthesky try to setup file delay config for your files or you can disable notifications for sync app.
  10. @SFarbo When a file in a shared folder in Selective sync mode is created and then deleted/moved while Sync is paused/busy with another task/has no other peers online, it cannot be synced to the other peers. Local peer notices the presence of a new file and after deleting it creates a placeholder. Other peers become aware of existence of such a file later, hence the warning sign, but in reality it is a "ghost file" that no one has anymore. Clicking on the warning one can see the filenames. If the files don't exist anymore, you can press the Ignore All button to hide the warning. One can also disable this warning via power user preferences: If the files exist, one should be careful - may be the more up-to-date version actually exists on a certain peer which is offline at the moment. If you are certain that local version of files is the most up-to-date, touch them or move them out of a shared folder to some temporary location and then move them back to the shared folder.
  11. @Hans#
  12. @Miyo there is no need to install it on windows. It's only a macOS issue.
  13. @Hans# Could you please send us logs?
  14. @dankshit Yes, you can set listening port manually.
  15. @Spike96 yep. It's a bug on Android. Thank you for your report!
  16. There is no any limitations. You can use as much drives as you want.
  17. Alex.

    Nik T.

    @NikT It's false positive.
  18. @7H0M4S Whitelisting Files And Folders Whitelisting works in a similar manner as ignoring, although you need to comply with one simple rule: whitelist rules must start with ! symbol (no quotes). Whitelist rules are always of higher priority than exclude rules, so their position in the list does not matter. You can use global IgnoreList in Profile to force agents to sync entires that are ignored by default IgnoreList. For example, default IgnoreList on each agent has entry ~* meaning that agents won’t sync items starting with a tilde. Edit global IgnoreList in Profile and add line !~* , all agents will start syncing new items starting with tilde. However, those that are already ignored, will stay ignored and not synced. To fix that you’ll need to recreate the job. To create pure whitelist, the first (ignore) filter should be all files * followed by a number of whitelist filters starting with !. For example, the whitelist allowing only synchronization of PDF files should look like: * !*.pdf
  19. @drego85 Did you restart Sync after you updated binary? Where did you place binary? How do you start Sync?
  20. @baudetd Sync will not sync files which has time stamp in future or incorrect.
  21. @Loftwyr could you please gather logs and mention the moment when it happened?
  22. @luomat Thank you!!! Right now we are working on a new version of Sync with bunch of fixes & great new features. I can't say exact date, but I'm crossing my fingers and hope it will be soon.
  23. @luomat No Please use the following build