• Content Count

  • Joined

  • Last visited

About uncovery

  • Rank
    New User

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. thanks for the explanation. I guess I should set the other peers to read-only instead.
  2. I have a shared folder that is synced between 2 of "my" devices and one other device. The main device (where all the files are) is a QNAP NAS (V 2.5.9 Build 1088). The folder there is set as read-only to make sure that other devices don't overwrite files on the NAS. The other devices are all set to "selective sync". Since some time, files and folders added to the NAS are not visible in the remote devices. Disconnecting and reconnecting them did not help. Restarting the remote device did not help either. The "history" menu on the NAS does not show that files have been added as well. Restarting the NAS did not help either. There are no errors on the history either. As far as I can tell, all other shared folders work perfectly. So how do I fix this? I find it highly concerning that I need to find out by accident that files are not being synced. There is no error, warning or similar. Is there another logfile on the NAS that I contains more information than the History view in the web menu? What can I do to fix this except for removing the folder on all devices and adding it again?
  3. There should be a process that allows people to erase the file history of a folder and make all connected machines assume that the folder is "new". Is a disconnect achieving that? Because then at least I could periodically dis-and reconnect a folder so reduce the RAM usage.
  4. I would like to know how Resilio - as a protocol and as a company - is treating privacy questions. Questions I have: Who can see the file names, folder names I am sharing? Is the traffic encrypted? What encryption method is used? Who has access to this encryption? Can someone sitting in the middle (a network admin) see the contents of files? See file names? Who can see my peer IP addresses? What impact does using a tracker server have on this? What impact using a relay server have? What kind of information are shared with Resilio as a company? Thanks!
  5. never mind, found the solution. This is unneccessarily cumbersome. Why can't there be a feature when you connect them that ask you what type of connection you want? https://help.resilio.com/hc/en-us/articles/206216565-How-to-create-a-Read-Only-folder-while-syncing-across-linked-devices-
  6. I am running the pro version of Resilio and want to connect a folder between two devices as read-only. How can I do that? I cannot find that feature setting in Advanced folders or "normal" ones.
  7. I am trying to install the latest version of btsyc on a CentOS 6.5 headless server. I cannot reach the WebUI. I configured the webui on port 65000. This is confirmed by the command line reply when I start the service: The service itself is configured to run on port 8888. When I run `lsof -Pnl +M -i4`, I get the following output: btsync 25687 500 9u IPv4 536416051 0t0 TCP *:8888 (LISTEN) btsync 25687 500 10u IPv4 536416052 0t0 UDP *:8888 btsync 25687 500 13u IPv4 536416060 0t0 UDP *:3838 Nothing else seems to be listening on 65000. I tried `netstat -tulpn` as well and the results are the same. I added a rule to iptables and `Iptables -L` returns (among others): But to make sure I tried to run it while the iptables service was completely switched off, and I still could not get any different results. The logfile sows the following: I tried to run webui on a different port, the result is the same. I also tried to bind the webui on my server's IP address instead of, same result. Any ideas? [Update] So I started this whole process again with a default config and on port 8888 and now it worked. As a recommendation for people in the future who have such an issue, try to use this command here: curl -k http://xxx.xxx.x.xxx:8888/gui -v to see if the server is running from the server's command line. It should show a quite long bunch of HTML if the server is running properly. If that works, try to amend the config file from there on