jbishop129

New Members
  • Content Count

    3
  • Joined

  • Last visited

About jbishop129

  • Rank
    New User
  1. Hey guys, Not sure if this discussion has moved elsewhere, if so let me know. It looks like BitTorrent has released v2.3, which brings the encrypted syncs in to the GUI, so we dont have to generate them manually. Is this likely to roll in to the builds we're working with here?
  2. I'm running the 1.4 Server unofficial package on 3 servers, and have ran in to a strange issue: Server A: all R/W syncs Server B: all R/O syncs Server C: all R/O syncs Server B and C are my read-only off-site backups. Recently I had a storage failure on Server C, and had to re-sync all of my Sync folders. the OS and therefore BTSync config was unaffected, only the mass-storage containing all the sync data. I fixed the storage, and since it was mapped to a new location, all the syncs on that node showed "Storage unavailable" (or 'path unavailable'? something like that). So I just removed the syncs from that node, then added them back in with the R/O keys from Server A. Back on Server A, the Peers list doesnt show the connection re-added from Server C (waited several hours). I thought maybe because it's the same server, and server A thinks it already has fully synced it, it's ignoring it for some reason. I went to Server A and did 'dpkg-reconfigure btsync' so I could run thru the settings, and I set the 'time to expire offline peers' to 0 days, so I would expire that failed Server C, then be able to just re-add, right? Things then went worse: Server A now shows no peers, even though Server B never went offline. I dpkg-reconfigure'ed again and set it back to 7 days, and peers are still all gone. On Server C, i do see it re-syncing from Server B, and it shows '2 of 2' peers, with both Server A and B listed. I can't figure out how to get Server A to see the peers again... not quite sure where I went wrong (although likely my setting the peer expiration to zero was bad).
  3. I second this! @tuxpoldo thanks for all your hard work and continued support on this build. I'd love to upgrade to v2.0 when available.