• Content Count

  • Joined

  • Last visited


About Helen

  • Rank
    Sync Support

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

2,531 profile views
  1. update Sync on your NAS. v2.3.x is too old. new version will work. you can download it from our site.
  2. what exactly did you paste there? Sync version? what error message did you receive, if any? any details or screenshots.
  3. Helen

    Latest desktop build 2.6.1

    please replace 2.6.0 with 2.6.1 in the link. I'll update the links there shorty. Thank you for pointing this out.
  4. Dear community, Sync release is now available. It's available via "Check now" (manual update) and is pushed to autoupdate. Also, you can get it via direct links below or from resilio.com site. Direct Download Links: Installer for Windows: x86 installer x64 installer Package for OS X: OS X package Gzip archive for Linux: arm armhf arm arm64 i386 x64 glibc23_i386 glibc23_x64 Gzip archive for FreeBSD: i386 x64 Deb and rpm: download here Android: arm x86 (if not sure which cpu your device has, use arm) Here are what's new and change log.
  5. Helen

    Latest desktop build 2.6.0

    Try these two things: 1) to update, just download exe file form our site and manually replace it in C:\Users\ghost\AppData\Roaming\Resilio Sync, name the downloaded file Resilio Sync.exe. 2) if that will be interrupted by open handles, unregister dlls from %appdata% and from C:\ProgramData\Resilio Sync with regsvr32 -i <file.dll> . After that try update. We'll see to change installation path.
  6. Helen

    Resilio selling clients emails

    @leopinheiro can you please send a sample of a spam mail. You can either send eml directly to me here or forward the mail to pro@resilio.com Refer to this forum post.
  7. Helen

    Downloading older versions?

    here https://forum.resilio.com/tags/build/
  8. Helen

    Resilio selling clients emails

    @leopinheiro, sorry to hear that you suffered the spam attack. Surely, Resilio is not selling the e-mails, but i've forwarded your report to the management to look into it.
  9. yes, indeed. these are child threads. DSM 6.2 shows these now.
  10. Can you please ssh to your NAS and run command "ps aux | grep sync" and show the output?
  11. Helen

    Can only link two devices

    Linking works correctly and allowing linking more that two or three devices. Again, please just take the M-key from one device and paste it to Sync on others. You just select a so-called master device and link other to it, not vice versa. Please contact support with exact steps that you do and a few screenshots.
  12. Helen

    Can only link two devices

    Crate identity on each device (or whatever setup you have now). Select the device to which you want to link others. Let it be device A. there go to Identity -> Link device. Copy the M-key and send it to other devices B, C, D..... There paste the M-key into 'Manual connection'. they will all link to A. If among B, C, D, E.... you have a mobile, then on A device show the QR code and scan it with a mobile device. It will link to A and others. This is how it works
  13. Helen

    Can only link two devices

    No, it's not a bug. When linking devices, it matter who you link to who. Please see it explained in this from topic, same case:
  14. Helen

    Sync is idle

    Do you mean that your devices are not connected to the internet? Then disable trackers so that Sync doesn't attempt to connect to trackers and thus does not give the error. Is there anything scpecific about the setup when peers are connected to each other and when they are not? When usually they are disconnected? Any details about be nice.
  15. Helen

    File deletions and Undesired actions. Warning!

    Thank you for your investigation and for sharing the results with others. let me add a few comments. Renaming and moving a file, as was mentioned on the forum, is actually deleting and recreating this file . Thus if a peer is in Selective Sync mode, it will put the old file to Archive, but it won't re-download the recreated file until instructed to. Thus, if you rename file on remote peer, the Selective Sync'ed peer will end up with a placeholder. What you have in red: 1) Original file deleted. It makes a erroneos 'replica' of the renamed placeholder file. The original file is LOST! - cannot reproduce this. If you rename a placeholder, other peers in Full Sync just rename the file and it remains in the folder. 2) Original file deleted. It makes a erroneos 'PH replica file' of the renamed placeholder file. The original file is LOST! - it's not lost, it's in .sync/Archive. See the comment about deleting/recreating the file. 3) The original file is DELETED! A useless placeholder is created in the destiny folder. - same as 2), it's not deleted, it's in Archive. Same applies for "Erase File and make a renamed PH" . And here comes warning - if this peer is the only one who had file, it won't be able to re-download it from anyone. That's how Selective Sync works. I'm not saying it's ideal behavior, we'll see to change it, but do not promise it'll be done in the near future.