uncovery

Members
  • Posts

    14
  • Joined

  • Last visited

Posts posted by uncovery

  1. 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?

  2. 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.

  3. 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

  4. 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?

  5. 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!

  6. 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:

    Quote

    Webui is listening on 0.0.0.0:65000

    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):

    Quote

    > ACCEPT     tcp  --  anywhere             anywhere            state NEW tcp dpt:65000

    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:

    Quote

        [20160521 17:24:25.687] Configuration from file "/home/includes/btsync/btsync.conf" has been applied
        [20160521 17:24:25.690] ZIP: Can't locate [version] in zip, error -100.
        [20160521 17:24:25.692] PLC[0x000000000225a8c0] binding on 0.0.0.0:8888
        [20160521 17:24:25.692] Socket[0x000000000225a8c0][9] bound listening socket 9 to IP 0.0.0.0:8888
        [20160521 17:24:25.692] UDP: bound listening socket 10 to IP 0.0.0.0:8888
        [20160521 17:24:25.694] test sha1: ****************
        [20160521 17:24:25.694] test sha2: ****************
        [20160521 17:24:25.694] test aes: ****************
        [20160521 17:24:25.694] Loading config file version 2.3.7, current version 2.3.7
        [20160521 17:24:25.694] My PeerID: 107408D3698D9BCA3EF7D****************
        [20160521 17:24:25.695] LC: LoadLicenses: there is no pro license
        [20160521 17:24:25.695] loaded history: 0 events
        [20160521 17:24:25.697] setup socket 13 for local peer discovery for 127.0.0.1: success
        [20160521 17:24:25.697] Debug log mask has been set to FFFFFFFF
        [20160521 17:24:25.697] Features mask has been set to 0
        [20160521 17:24:56.835] OpenSSL: Loaded X509 trusted CA from "/etc/pki/tls/certs/ca-bundle.crt"

    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