ms2oo8

Members
  • Content Count

    34
  • Joined

  • Last visited

About ms2oo8

  • Rank
    Advanced Member

Recent Profile Visitors

521 profile views
  1. So I've tried to install Resilio on Centos 7 by following the instructions in the FAQ. I get stuck when I try to log into the web interface. The server is hosting in AWS with a static IP attached. I've edited the AWS Security Group to allow port 8888 and by all appearances Resilio is listening on port 8888, but no joy yet. On the server Firewall ports are open [root@control ~]# firewall-cmd --list-ports 443/tcp 49152-65535/tcp 139/tcp 138/tcp 6789/tcp 8888/tcp 80/tcp 20-21/tcp 8000/tcp 445/tcp 1088/tcp 137/tcp 901/tcp 22/tcp Resilio is listening on port 8888 [root@con
  2. just to reiterate the post here, we're currently syncing 3.79 TB of files (hundreds of thousands of files). Our Sync status is "Indexing" all the time, but as far as I can tell, it's keeping files up to date.
  3. so the latest is safe to upgrade from now? Or are we still waiting for a fix to this issue before it's considered stable to upgrade?
  4. I have this issue as well and I'm running 2.3.1 so i don't think it's an issue due to 2.3.3 Parts of this site, including the forum and other help sections have had intermittent connectivity over the past few days. My assumption is that maybe the tracker servers are experiencing the same intermittent connection, causing this message in all clients, regardless of client version.
  5. a few questions. did you isntall btsync on the NAS? iow is it the NAS hardware / cpu / ram that you're using to index your 3.7TB of data? To sync that many files and folders could require more RAM than your device has built in. We've run into similar issues syncing a similar amount of data. We're currently making out ok, thought it's not been entirely troublefree, by using dedicated Windows desktop clients to run the Sync software with mapped UNC drives. There has been issues previously with performance on mapped UNC drives. We do think that we're getting close to the point
  6. I'm having the same issue. Files are in the quene, the log says they uploaded, but they don't appear on the remote peer. The folders get created, but the files don't upload.
  7. I have a .journal file that is sitting at 13GB. What do these files do and is there anything I can or should be doing to limit the size of this file?
  8. Upgrading to Yosemite fixed this issue.
  9. anybody? Is this simply a limitation of the Mac version?
  10. Title says it all. I'm trying to link a device, so I copy the key from the first 2.0 device, go to my second device and click Link a Device already running Sync 2.0, click Link to a Desktop device manually, paste my key, and click link. The message saying that connecting can take as long as 60 seconds, comes up, and stays up forever. The device never links successfully. The only way I'm abe to get new devices connected eventually, is to create a new ID for each device, and then share a folder link from the original sync device, and eventually they connect. as an aside, both devices are desk
  11. On Windows I can right click and "Sync to this device" for an entire folder or sub-folder. On Mac, this function seems missing, and I need to drill to the file level to get this fucntionality. How do I sync an entire folder with subfolders and files on Mac, without manually going into each sub folder to right click and download to the mac?
  12. Thanks Sorry for being anxious about this bug. We bought about $2000 of hardware that we were planning to use with Sync, which is now sitting idle due to this bug. I'll sign up for 2.0, see if it works then.
  13. Is this bug being tracked in your system? Also when is 2.0 ready for testing?