chicagonyc

Members
  • Content Count

    23
  • Joined

  • Last visited

About chicagonyc

  • Rank
    Member
  1. I've been running a licensed version Resilio Sync happily on my Windows 10 Pro machine. I recently successfully installed Windows Subsystem for Linux 2 (WSL2), and then Ubuntu 20.04. It runs very well. I am running RStudio Server on this machine to allow me to access remote computing resources. One thing that's very attractive about WSL2 is that it allows read/write access to the Windows file system (ie, /mnt/d/Work/). The folder I am interested in having Linux have access to is synchronized with Resilio Sync. The idea being that if I change a file in Linux, it is immediately reflected on
  2. Remirus was super helpful. I basically looked through the logs and saw some temp files which " failed to verify signature ". I just deleted them. Once I did that the sync worked perfectly. I'm not sure about the version though. I had 1.4 before upgrading to 2.3.6. I do still have the bug on another folder I'm trying to sync. Here, the failed to verify signature is attached to a folder, not a bunch of temp files.
  3. I have BTsync 2.3.6 installed on a variety of Windows 8.1 x64 machines, and it's worked fine since I upgraded from 1.4. I have a large collection of folders that I sync successfully, some very large (nearly 200 Gb). I installed BTsync 2.3.6 on a new Windows 10 x64 machine, and I copied all my files from my old computer to the new one. I knew that BTsync is good about not re-transfering identical data, so I just added all the folders to the new machine and let them go about re-indexing. Everything went perfectly for every single folder save one. This one has about 80k files and 77 Gb of da
  4. +1. No info on when indexing will finish (if ever) on a largish folder (77Gb, 70k files)
  5. Update: I'm able to do this once I click off "Simple Mode" in the Advanced options -- which I never noticed before. Now 2-way syncing works perfectly in 2.3.6. But it probably shouldn't be hidden like this. I can imagine lots of people liking the ability to essentially manage their phone's DCIM folder directly from the computer. With the 1.4 version of BTsync app on my Android phone (Oneplus One updated to Marshmallow), I was able to add my phone's internal camera folder (/storage/emulated/0/DCIM/Camera) as an ordinary sync folder. That is, not as a "backup" folder. Why would I want
  6. Ok, this works. Maybe the user should be alerted more about this issue as it's not obvious the relevant owner changes between the two versions. Otherwise everything looks great.
  7. Yes, but I'd ask you if you could remind me how! Ok, is this the right tool for the job: "chown -R admin folderpath"?
  8. I just upgraded my Windows machines from 1.4 to 2.3.6 and the updates went perfectly. All the shared folders I had in the old version carried over into the new. Then I wanted to upgrade my Synology (5.x) installation of BTSync to 2.3.6. So I stopped the old 1.4 package, and uninstalled it. Then I manually installed 2.3.6. That went fine. But when I started the package, it had forgotten the very lengthy list of shared folders. Ok, fine, I can enter those manually (though it's a lot of work). But when I entered the read only key that I use for one of many shared folders, I got a w
  9. For 1.4 too? Sent from my Nexus 7 using Tapatalk
  10. Any update on this? The x86-powered $199 Asus Android phone is very impressive -- but not if it can't run BTSync!
  11. Thanks to Helen, we're getting somewhere. After SSHing into my NAS, I have discovered that the owner of the btsync binary is "btsync". Eg, when I search for btsync (ps | grep btsync) I get: 18690 btsync 475m S /usr/local/btsync/bin/btsync --config /usr/local/bts But I infer that "btsync" the account doesn't have enough privileges. And I don't see the "btsync" account in my list of users to elevate its privileges. And the shared folder I want to sync on the NAS is owned by "root". So do I change the owner of btsync to "root" or do I change the owner of the folders "btsync"? The very c
  12. The only way I have been able to get around this problem is changing permissions to 777, eg, chmod 777 /volume1/Videos But isn't this a bit strange? And insecure? From my limited Unix understanding, I created a "user" within BTSync which has no permissions to write. But ... I don't see this user in my Synology control panel. So how can I give this user permission to write to the bunch of shared folders that I have created?
  13. Any ideas anyone? I haven't done anything special. I'm an advanced Windows user (admittedly a bit weak with Unix) with a new Synology-compatible NAS, which is supposed to have a GUI interface for BTsync. I run BTSync and the first thing I try to do is add a new sync folder -- whereupon I get the write permission error. Surely this isn't a unique use case....
  14. Ok. How? ps Shouldn't it be easier to, within the GUI, logout, and/or login as one of the machine's users?
  15. Hello, I have been happily using BTsync with my Windows machines without any issues. I just set up a new Synology NAS and installed BTSync 1.4.103 with the SynoCommunity GUI install. That part worked perfectly. I was asked for the name of the server, as well as to set up an account. I did so and the web interface started up. When I try adding a folder or connecting to an existing key, I get the "no write permissions for selected folder error". I'm a relative novice with using Linux based systems, so I'd prefer to avoid having to use a command line. It looks to me like the account I wa