yottabit

Members
  • Content Count

    143
  • Joined

  • Last visited

  • Days Won

    2

About yottabit

  • Rank
    Advanced Member
  • Birthday 02/15/1978

Profile Information

  • Gender
    Male
  • Location
    Dallas, TX, US
  • Interests
    Fiber-optic transmission, carrier Ethernet services, public-band microwave, firewalls, routers, computer hardware, NAS, Linux, FreeBSD, Windows, Android, MikroTik RouterOS & Routerboard, coffee roasting, beer brewing, fixing tractors and vehicles ... more interests than time!
  1. Fool me once... Yeah, I'm with Syncthing now and never going back to Resilio. I do miss encrypted at-rest and selective sync, but I can live without them.
  2. I've migrated all Resilio Sync workloads to Synthing. Working perfectly, couldn't be happier. A little sad though, since I used btsync since its early alpha days. But I can't deal with the bugs and lack of updates to fix those bugs. Only thing I'm missing from Syncthing is the easy of sharing with just a public key, and having the ability to use a node as encrypted storage. I rarely use encrypted storage though, so oh well, I'll do something else if I ever need it again. By, Resilio! Good luck!
  3. Andy, that won't work for me. I use Google Photos to backup my photos and reclaim the space from my phone. If I use a standard share from Sync, then my backups on my own server would be deleted when Google Photos purges the local storage on the phone. I use ZFS and daily snapshots, so I could always reconstruct the photos, but that's a huge hassle I would rather not deal with. For now, I have used a regular share to backup Signal as I don't need every backup file, like I would with photos. I guess it's time to start taking a more serious look at SyncThing. It's just a shame sinc
  4. It seems we may be out of luck. It doesn't look like the Android app is even being developed anymore, judging by how far behind it is compared to the desktop version. Sigh.
  5. I have created a photos backup with the Android app and it's working great. Now I want to create a new custom backup for my Signal backups. Add Add backup Custom Navigate to path Choose Folder Add Immediately taken back to the Folders list and the new backup definition is not present Anyone else run into this? Any workarounds? Version: 2.6.4 (8693) on Android 10, Google Pixel 3.
  6. The FreeBSD x64 build of this version cannot write large files. I am trying to sync 50 GiB files. Reverting to 2.6.1 solved the problem for me. This can also be found as a solution for many experiencing the problem in FreeBSD jails, via the FreeNAS forums. Is there any plan to fix this? It's been 8 months...
  7. Ever since upgrading to 2.3.6 on FreeBSD 64-bit, after 1-2 days the syncs stop and I cannot login from the webui (keeps prompting for login over and over again with no errors). I have to kill the process, restart, and then back in business. Nothing in the log, even with debug enabled, to indicate there's a problem. Seen this yet? I've submitted a bug over the past weekend.
  8. @AlexanderD, thanks! Sorry but time got away from me before I was able to investigate further. Since upgrading to .128 it seems the .120 problem has been fixed. I still have two shares that had long-standing problems that I need to check.
  9. Seems to have fixed the syncing issue I had in .120. Thanks!
  10. I am having this "Will try to find peer for file ..." message in the debug log for many shares... nothing seems to be sync'ing now with this 2.0.120 version. I am using all Legacy 1.4 key-based sharing. Do you guys need any more logs? Do you have any test builds that may fix?
  11. I had sync'd 750 GB of files from my home NAS (FreeBSD) to a Linux VM on Google Cloud Platform (GCP), using EROS from NAS -> GCP. I was doing it to test a difficulty I had sync'ing to my friend's FreeBSD NAS with the same EROS where it would just stall at a high number of files remaining and never continue, no matter what we did (check UPnP rules on routers, create static port mappings, restart btsync, delete and re-add secret, etc.). Finally he deleted the EROS share and all data, and added it back at the same time I added the EROS to my GCP. Three-way sync started immediately and comple
  12. +1 Just tried to update 1.4 on my FreeBSD x64 box to 2.0 and can't hit the web gui no matter how I try. I'm open to running a test build to see if it fixes the problem. And I followed this topic so hopefully when I fix has been rolled out, Helen@ will ping this thread.
  13. Here's the log trail from the RO-enc 1.4 node: [20150218 21:25:36.447] SF[EDC6]: Torrent /mnt/jacob.mcdonald/NC7TZU6AGVVR7RM26AV2S2JER6BZ2RFLNWCDMSQ/FCT4GVBDOK3KFUB4KIJWHA6DVU/26JMPM2OYX4PB4U6YYUCAEFDY4S4PKMZJ7IPV4W7CABF2UVNNKH Q/7UHLBRBDX5MGH3ZVXUK4HISGYM/6PNX5UAIG6EJWCZMCNJAR44MW4 status:137 error:<NULL> meta:1 conns:0 io:0 [20150218 21:25:36.447] SF[EDC6]: Torrent /mnt/jacob.mcdonald/NC7TZU6AGVVR7RM26AV2S2JER6BZ2RFLNWCDMSQ/FCT4GVBDOK3KFUB4KIJWHA6DVU/26JMPM2OYX4PB4U6YYUCAEFDY4S4PKMZJ7IPV4W7CABF2UVNNKH Q/7UHLBRBDX5MGH3ZVXUK4HISGYM/5CLBYZL65W6BLYJ34RCDXKL32E status:137 error:<NULL>
  14. EDIT: edited for clarity Hi Helen, This is a one-way sync to two other nodes (1x RO & 1x RO-encrypted). All nodes were originally 1.4. The source node remains 1.4. The RO node was upgraded to 2.0. The RO-enc share remains at 1.4. The source 1.4 node reports that 82 GB (26,398 files) of the 722 GB total still needs transferred to the RO 1.4 node. The RO-enc node is not finishing the sync, either. The source 1.4 node reports it needs to send 133 GB to the RO-enc node, and the RO 2.0 node reports it needs to send 63 GB to that same RO-enc node. Source 1.4 node log tail: [root@nas1]