Wurstmann

Hey, my sync.log is flooded with these log entrys. Is there something that i have to do to fix this? [2023-12-10 18:40:23.897] TLSPSK[0x000001d808b4c240]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.897] TLSPSK[0x000001d808b4c420]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.897] TLSPSK[0x000001d808b4a800]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.898] TLSPSK[0x000001d808b4c7e0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.898] TLSPSK[0x000001d808b4c060]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.898] TLSPSK[0x000001d808b4d230]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.898] TLSPSK[0x000001d808b499f0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.898] TLSPSK[0x000001d808b4af80]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.898] TLSPSK[0x000001d808b4b160]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.898] TLSPSK[0x000001d808b4bca0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.898] TLSPSK[0x000001d808b4b340]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.898] TLSPSK[0x000001d808b4b430]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.898] TLSPSK[0x000001d808b4b610]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.898] TLSPSK[0x000001d808b4be80]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.898] TLSPSK[0x000001d808b4c150]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.899] TLSPSK[0x000001d808b49cc0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.899] TLSPSK[0x000001d808b4c330]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.899] TLSPSK[0x000001d808b49db0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.899] TLSPSK[0x000001d808b49ea0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.899] TLSPSK[0x000001d808b4c510]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.899] TLSPSK[0x000001d808b4d6e0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.899] TLSPSK[0x000001d808b4d9b0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.899] TLSPSK[0x000001d808b4db90]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.899] TLSPSK[0x000001d808b4d500]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.899] TLSPSK[0x000001d808b4d7d0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.900] TLSPSK[0x000001d808b4daa0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.900] TLSPSK[0x000001d808b4d8c0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.900] TLSPSK[0x000001d808b47290]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.900] TLSPSK[0x000001d808b49810]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.900] TLSPSK[0x000001d808b46fc0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.900] TLSPSK[0x000001d808b48280]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.900] TLSPSK[0x000001d808b46b10]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.900] TLSPSK[0x000001d808b470b0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.900] TLSPSK[0x000001d808b46390]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.900] TLSPSK[0x000001d808b46840]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.900] TLSPSK[0x000001d808b49360]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.900] TLSPSK[0x000001d808b46480]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.901] TLSPSK[0x000001d808b49090]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.901] TLSPSK[0x000001d808b47470]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.901] TLSPSK[0x000001d808b48370]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.901] TLSPSK[0x000001d808b48640]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.901] TLSPSK[0x000001d808b47380]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.901] TLSPSK[0x000001d808b47ce0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.901] TLSPSK[0x000001d808b46570]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.901] TLSPSK[0x000001d808b48190]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.901] TLSPSK[0x000001d808b471a0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.901] TLSPSK[0x000001d808b46c00]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.901] TLSPSK[0x000001d808b47560]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.902] TLSPSK[0x000001d808b47740]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.902] TLSPSK[0x000001d808b45d00]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.902] TLSPSK[0x000001d808b45df0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.902] TLSPSK[0x000001d808b45ee0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.902] TLSPSK[0x000001d808b47830]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.902] TLSPSK[0x000001d808b47920]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.902] TLSPSK[0x000001d808b47a10]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.902] TLSPSK[0x000001d808b45fd0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.902] TLSPSK[0x000001d808b47b00]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.902] TLSPSK[0x000001d808b460c0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.902] TLSPSK[0x000001d808b48fa0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.903] TLSPSK[0x000001d808b47bf0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.903] TLSPSK[0x000001d808b48910]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.903] TLSPSK[0x000001d808b48460]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.903] TLSPSK[0x000001d808b47ec0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384 [2023-12-10 18:40:23.903] TLSPSK[0x000001d808b462a0]: Supported ciphers: DHE-PSK-AES128-GCM-SHA256:DHE-PSK-AES256-GCM-SHA384

Nope, Client A and Client B has both folders. Folder A should keep sync files between Client A and B every time possible over Internet or Local. But Folder B should only bei sync when both clients are on a local network

I have two clients that each have the following folders in Resilio Sync Folder A (Small Files, to be synchronized via the Internet) Folder Preferences search_lan=1 use_hosts=0 use_relay_server=1 use_tracker=1 Folder B (Big Files, should only be synchronized via LAN) search_lan=1 use_hosts=0 use_relay_server=0 use_tracker=0 However, the settings for Folder B are not applied. The exchange of data takes place even if the two clients are connected via the Internet in different locations.

Hello Folks, Is there a way to disable debug logging in resiliosync via config?

push no one here who can help me

Hello Resilio-Team, I am trying to get the JSON output from "http://127.0.0.1:****/api/v2/folders/activity" with the following code: <!doctype html> <html lang="en"> <head> <meta charset="utf-8"> <script src="https://code.jquery.com/jquery-1.12.4.min.js" integrity="sha256-ZosEbRLbNQzLpnKIkEdrPv7lOy9C27hHQ+Xp8a4MxAQ=" crossorigin="anonymous"></script> </head> <body> <script> $(document).ready(function() { $.ajax({ url: "http://127.0.0.1:50136/api/v2/folders/activity", cache: true, dataType: "jsonp", jsonp: false, jsonpCallback: false, type: "GET", complete: function(result) { alert(result); }, success: function(result) { alert(result); }, error: function(result) { console.log(result); } }); }); </script> </body> </html> Chrome Network Monitor seems to look fine: But everytime i got an error message in console: Can some one help to fetch that json data correctly?