uncovery

Yeah so the hoster has another level of firewall on their side that I needed to configure... So this is solved.

Hi there, I am running on Almalinux 9. It is running perfectly on the same OS on a different computer/hoster... I installed via the repo, so I have the version 2.7.3 I disabled SELinux I disabled firewalld I changed the IP in the config to 0.0.0.0:8888 I can see the server listening on the port when running netstat. The logfile states: 20HttpListenConnection::listen[0x000055f4799f20d0][16] bound listening socket 16 to IP 0.0.0.0:8888 The logfile also shows this here (ASCII Codes removed) [20240229 15:55:05.434] Debug log mask has been set to FFFFFFFF [20240229 15:55:05.434] Features mask has been set to 0 [20240229 15:55:05.434] Scheduler: Apply global rule, download limit: -1, upload limit: -1 [20240229 15:55:05.434] CoreState: Total memory: 33525788672, used by Sync: 31690752, percentage used: 0.09 [20240229 15:55:05.434] CoreState: Cpu load: 0 [20240229 15:55:05.434] CoreState: Process cpu load: 0 [20240229 15:55:05.434] CoreState: Network interfaces: [20240229 15:55:05.435] CoreState: Interface name: eth0 mac: d0:50:99:fa:0b:1c [20240229 15:55:05.435] CoreState: Addr: MY.IPV4.CORRECT:0 [20240229 15:55:05.435] CoreState: Addr: MY.IPV6.CORRECT:0 [20240229 15:55:05.435] CoreState: Interface name: eth1 mac: d0:50:99:fa:0b:1d [20240229 15:55:05.435] CoreState: Interface name: lo mac: 00:00:00:00:00:00 [20240229 15:55:05.435] CoreState: Addr: 127.0.0.1:0 [20240229 15:55:05.435] CoreState: Addr: [::1]:0 [20240229 15:55:05.435] CoreState: Interface name: usb0 mac: fa:ca:80:8e:6a:67 [20240229 15:55:05.435] message thread start [20240229 15:55:05.435] SYS_RES: drive "/", id: 2308, capacity: 927718088704, free_space: 763769192448 [20240229 15:55:05.435] SYS_RES: drive "/boot", id: 2306, capacity: 1403977728, free_space: 1155911680 [20240229 15:55:05.491] HTTP[]: GET /e?.... HTTP/1.1 [20240229 15:55:05.491] HTTP[]: Host: i-2000.b-2-7-3.sync.bench.resilio.com [20240229 15:55:05.491] HTTP[]: User-Agent: Resilio Sync [20240229 15:55:05.491] HTTP[]: Accept-Encoding: gzip [20240229 15:55:05.491] HTTP[]: Connection: close [20240229 15:55:05.548] HTTP[]: RESP_CODE: 301 [20240229 15:55:05.548] HTTP[]: RESP_HEADER: Server = "nginx" [20240229 15:55:05.548] HTTP[]: RESP_HEADER: Date = "Thu, 29 Feb 2024 07:55:05 GMT" [20240229 15:55:05.548] HTTP[]: RESP_HEADER: Content-Type = "text/html" [20240229 15:55:05.548] HTTP[]: RESP_HEADER: Content-Length = "162" [20240229 15:55:05.548] HTTP[]: RESP_HEADER: Connection = "close" [20240229 15:55:05.548] HTTP[]: RESP_HEADER: Location = "https://i-2000.b-2-7-3.sync.bench.resilio.com/e? [20240229 15:55:05.548] HTTP[]: RESP_BODY: {...} size 162 [20240229 15:55:05.548] HTTP[]: closing [20240229 15:55:05.599] HTTP[]: destroying Still, when I try to access the remote headless server on the IP with port 8888, I get a timeout. Any idea what else I could look for?

Sometimes a device might fail to sync because there is a database issue. There is no way of knowing that this happens unless one opens the web interface of the device. It would be great if there was an alert sent via email or to connected devices. Right now connected peers have no idea that one of the nodes is unable to sync.

I wanted to ask how Resilio is currently protecting the web interface against brute-force attacks? I could not find any relevant settings in the config. Also, is there an options to activate 2FA for the web interface? thanks!

Thanks for the advice. I get this line in netstat: tcp 0 0 127.0.0.1:8888 0.0.0.0:* LISTEN - I stopped firewalld, but it still does not work.

Hi, thanks for the help. My config file has that already: "webui" : { "listen" : "0.0.0.0:8888" // remove field to disable WebUI This was there without me adding it. Should that be enough? I am a bit confused because the export of the config file does not seem to match 100% the actual settings in the client, e.g. I disabled uPnP but it's ON in the config that was exported.

Hey guys, I just freshly setup Resilio on a PC running CentOS stream. I can access the web interface on the same PC with https://localhost:8888/ but not from another computer I have made sure that the firewall has tcp port 8888 open (it should work, I have another service running, opened the firewall and there it works as well). Any idea what I can check to fix this matter? Is there any setting that needs to be set to access the webUI from another computer? thanks

thanks for the explanation. I guess I should set the other peers to read-only instead.

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?

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.

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!

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-

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.

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 0.0.0.0, 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