Search the Community

Showing results for tags 'peer'.

  • 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 7 results

  1. Hi there. I have been a resilio sync user for a while and I have synced a lot of data. I have 4 devices which I keep synced, my phone, work laptop, another laptop and a raspberry pi. The folder on raspberry pi is set to selective sync on each of the devices. Now for some reason, after syncing a 7 or 10 gb file to my pi, sync has stopped detecting my pi altogether. On my pcs, even if on the internet (not lan), it will not show up. But strangely enoiugh, on my phone the pi shows up (not on lan). So I am not sure what caused this. There was no update on either of my devices to cause this issue. I
  2. hi I'm new to Resilio Sync. I've shared my first folder from my server with my first peer, and all is well; peer 1 pulls down the data. When I share the same folder to a second peer, the second peer pulls down data in the folder as expected, but only ever 'sees' the server. The peers do not see each other, although do have an entry under 'inactive' for each other, noted as 0 of 0 peers. Both shares are as Read Only. Its like my peers don't like each other, and will only see the server from which the share was 'issued'. The server see the first peer, and shows the secon
  3. Admittedly I have little knowledge of sharing files in this manner. How do I establish a peer and what exactly is that? How can I access the ID when I have no idea what app to use? I've paid for this, but in my ignorance do not find it user friendly and can't even find an address to request a termination and refund. After hours of trying, I am giving the forum a shot - maybe someone will have pity on my lack of how to do this sort of thing. DeAnn
  4. I've posted about this before and was told "no updates at this time," but this is a pressing need and a very easy fix. Please, remove the 50-peer hard cap in BT Sync!! Abolish it, raise it significantly, or add a GUI option to let it be configurable, This cannot be a difficult change, and I can't imagine what possible negative effects there could be. I'm attempting to host some projects for people to use and am constantly bumping into this hard peer cap issue. I know the team is very busy, but this would be extremely helpful if you could find time to implement it. Thank-you.
  5. Android sync version is there away to get a list of the peers. it will give you the number of peers but I would like to be able to get the peer name and where thay are sync or not.
  6. Hello, First of all, sorry for my bad english. I would like to cover a folder at my server with bitsync, automatic I will add a few files that are backups from my database, they will sync correctly and work fine, but when I delete these files from my server, I would like to not delete it from the other peer. I notice a few things about the permissions, Read and Write, but when I create only to read, the files add will not be sync and with the other peer. Well, is there any sugestion to add files, sync and then remove the add files from one of the sources? Best regardĀ“s.
  7. System A (Synology NAS) w/ btsync 1.3.109. Share 'Repository' has settings relay server, tracker, LAN, not DHT. System B (x64 Linux) w/ btsync 1.4.83. Share 'Repository' has settings relay server, tracker, LAN, not DHT. The shares are connected and synched. Only these two systems are involved. On system B, I change the settings to LAN only. After a while both systems report that there are no peers to connect to. Restarting btsync on system B will re-establish the connection. I guess a restart on system A would have helped as well. I think btsync should re-establish the connection after