Search the Community

Showing results for tags 'unsupported or empty sync.dat file'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 1 result

  1. Hey all, Updating to the latest sync has removed my pro license and all of my shares. I'm running the latest rslsync (2.4.1 (672)) which I updated from 2.4.0 (666) today I downloaded 2.4.1 from: I am running Linux (Ubuntu 14.04.5 LTS (GNU/Linux 3.16.0-70-generic x86_64)) I paused all of my shares, waited for all syncing to stop, I did a pkill on the process, and then I updated. After updating, I relaunched via the command line with my previous config (see below: xxx represents removed config data) { "device_name": "xxxxxxx", "listening_port" : 0, // 0 - randomize port "storage_path" : "/home/xxxxxx/.sync", "check_for_updates" : true, "use_upnp" : true, // use UPnP for port mapping "download_limit" : 0, "upload_limit" : 0, "folder_rescan_interval" : 86400, "webui" : { "listen" : "", "login" : "xxxxxx", "password" : "xxxxxx" } } When I re-opened the web interface, it invited me to try pro. I have re-added my license, and this is fine now. However, what I can not do is see any of my syncs. Obviously the data is there, but the web interface just says "You don't have any folders. Add one and start syncing": Before the upgrade I had 9 different folders. Is this a known issue with switching from 2.4.0 to 2.4.1? Is there anything I can do to recover other than to re-add all of my syncs and let them re-index? I can ssh/port forward to get to the web interface on my remote boxes and grab the keys from there, but it would be nice not to have to re-index a couple dozen TB of data. I have tried reverting back to 2.4.0 but the problem still persists. I tried on a new server (Which I had just finished syncing all my data to) and had the same problem. Sorry if this has already been posted. I had a cursory glance at the troubleshooting post titles and couldn't see a similar topic.