Helen

Administrators
  • Posts

    2,719
  • Joined

  • Last visited

Posts posted by Helen

  1. Dear community,

    Sync 2.6.0 Release Candidate is now available. You can get it via direct links below only. 

    Direct Download Links:

    MAJOR CHANGES

    Improved transfer speed

    • File send is free now
    • Introduced performance graphs

    FIXES AND IMPROVEMENTS (compared to RC 2.6.0.1298)

    • Core improvements
    • Fixed syncing after changing its letter case on Windows
    • Improved warnings for invalidated files in Read-only shares
    • Fixed some crashes

     

      Screen Shot 2018-05-22 at 11.34.50 AM.png

    • this error means that Sync was not able to find the share by the path from share prefs. May be SD card gets mounted way later after reboot or it changes its identifier. Doublecheck the path to share in Sync and in system. Also, try disabling Sync autostart and start it manually after reboot.

    • Please contact support with any details about your case and Sync version. The latest iteration between support and leoeavenson was: 
       

      >I have the most recent version
      Which exactly version do you have? The most recent for today is 2.5.6. (for today it's 2.5.12)

      > blank browser page with my DDNS followed by :8888
      Check the following:
      Check that dns name resolves into the address which is available from the network location you're currently in. Try using the IP address of the NAS instead. The listening port of webui shall also be open. 
      Do you see gray bar at the top of the page?
      Check that Sync process is actually running - ssh to your NAS and check with command "ps aux | grep sync"
      How many shares you have in Sync and how many files are there?
      how much RAM does you NAS have and how much of that Sync consumes.

    • this error pop ups if UTC timestamp on peers differs by more than 10 minutes. All peers shall have it the same, taking into account their local time and timezone, so check these in first place. Re-sharing a folder will not help here. 


      This article will help to to verify the timestamps . To avoid further misunderstanding, I'll provide some comments ahead. UTC time shows the devices time relatively to Greenwich. 
      So if peerA is in (UTC +01:00), and peerB is in (UTC +03:00) time zone, the local time of peerA will be, for example, 13:45, and for peerB 15:45 accordingly. However, their Greenwich time will be still the same peerA = 12:45 = 13:45 minus 1 hour, for peerB = 12:45 = 15:45 minus 3 hours. 
      If either of the setting is wrong,  you get that error message: for example, on peerB you set "the correct time" - some 14:35, and get that its UTC is now 14:35 minus 3 hours = 11:45, and get 1 hour timediff with peerA.