All Activity

This stream auto-updates     

  1. Today
  2. @Phillmac It looks like some app is using these ports. Please check it with the following command netstat - ano | findstr <port_number>
  3. It's not possible to do with Resilio Sync. Sync will not remove any files before syncing in destination folder. As a workaround you can point Sync to a fresh new destination folder without unnecessary files or delete files manually and then start syncing or you can use Resilio Connect which can start pre & post syncing scripts which will delete unnecessary files.
  4. Just a simple option to run Resilio minimized on startup would mean a lot to me. I use resilio for PC - Phone sync and i don't use it every day, so i don't like it showing up in my face every time i turn on PC, instead i turned off startup option, and open it only when i need to. Option to start it minimized would be really cool!
  5. Hello Alex! Did you understand the problem right? It’s not a problem to sync files with the same hash. The problem is to remove files that were in the destination folder before sync.
  6. Just create read-write share between source and destination peers. This folder will be synced. If you remove file on first peer, then it will be removed on the second. You will get identical amount of files and folders. https://help.resilio.com/hc/en-us/articles/205506699-Quick-guide-to-syncing
  7. Frank, thank you for the answer! It’s not a one time thing. I deal with that all the time and folders are very big (1,5 Tb). I often change computers (it has its own specifics) and I don’t want to rewrite large volumes or wait when it will be sync. So I use pre-populated folders. I thought about something like FreeFileSync. It’s interesting could it work not only in the same network but over internet too?
  8. @Dovid if you need to sync Windows permissions (ACL) please use Resilio Connect https://www.resilio.com/sync-vs-connect/
  9. @zinjashike yeah, our Android client can't sync % sign in file names properly. Will be fixed in next releases.
  10. It's a one time thing? You have two folders, which you want to keep in sync, but at the moment they are out of sync and now you ask for a solution, to bring them in sync, so Resilio Sync can keep them in sync in the future? Use a third part tool, like FreeFileSync, select both source and destination. Let it compare both folders and select the desired action (copy, remove) for each out of sync folder pair. Then let it run. Afterwards set up Resilio Sync on both source and destination to keep both folders in sync in the future.
  11. Yesterday
  12. Greetings, I've encountered a bug when syncing from Windows to Android using Resilio. Files that have a percent sign in their name have the percent replaced with a black diamond with a question mark on sync. When Resilio runs into the issue it will attempt to repeatedly sync the same file. This does not appear to be an encoding error as a SMB sync worked fine from a different application. After I sync/copy the file using another method I can then allow Resilio to process the file without issue - it does not enter into a sync loop if that makes sense. Thank you.
  13. Soon after starting the service, the log is full of entries (see below) and the service fails to listen on the configured port, finally picking a (seemingly) random port to listen on. sync version: 2.6.3 (1340) (server) [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56125 [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56125 [2019-11-21 10:25:17.607] UDP: UDP port bind failed 0.0.0.0:56125: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56126 [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56126 [2019-11-21 10:25:17.607] UDP: UDP port bind failed 0.0.0.0:56126: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56127 [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56127 [2019-11-21 10:25:17.607] UDP: UDP port bind failed 0.0.0.0:56127: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56128 [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56128 [2019-11-21 10:25:17.607] UDP: UDP port bind failed 0.0.0.0:56128: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56129 [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56129 [2019-11-21 10:25:17.607] UDP: UDP port bind failed 0.0.0.0:56129: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56130 [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56130 [2019-11-21 10:25:17.607] UDP: UDP port bind failed 0.0.0.0:56130: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56131 [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56131 [2019-11-21 10:25:17.607] UDP: UDP port bind failed 0.0.0.0:56131: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56132 [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56132 [2019-11-21 10:25:17.607] UDP: UDP port bind failed 0.0.0.0:56132: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56133 [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56133 [2019-11-21 10:25:17.607] UDP: UDP port bind failed 0.0.0.0:56133: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56134 [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56134 [2019-11-21 10:25:17.607] UDP: UDP port bind failed 0.0.0.0:56134: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56135 [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56135 [2019-11-21 10:25:17.607] UDP: UDP port bind failed 0.0.0.0:56135: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.607] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56136 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56136 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56136: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56137 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56137 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56137: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56138 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56138 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56138: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56139 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56139 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56139: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56140 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56140 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56140: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56141 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56141 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56141: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56142 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56142 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56142: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56143 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56143 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56143: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56144 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56144 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56144: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56145 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56145 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56145: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56146 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56146 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56146: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56147 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56147 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56147: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56148 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56148 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56148: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56149 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56149 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56149: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56150 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56150 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56150: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56151 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56151 [2019-11-21 10:25:17.623] UDP: UDP port bind failed 0.0.0.0:56151: (10048) Only one usage of each socket address (protocol/network address/port) is normally permitted. [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafb40][596] bound listening socket 596 to IP 0.0.0.0:56152 [2019-11-21 10:25:17.623] class PeerListenConnection::Socket::listen[0x000001a23ecafbc0][1028] bound listening socket 1028 to IP [::]:56152
  14. Last week
  15. Hello! Can anybody explain me, If I want to sync non-empty pre-populated folder with source folder how can I achieve identity? As I understand right, the files placed in the destination folder before sync will leave there. How can I do a synchronization like in DropBox service — files in source and destination folders will be the same, nothing extra? Or, if asked differently how to automatically remove unnecessary old files from destination folder? Sorry for my English, Konstantin
  16. It sounds similar to the topic below, but it seems to be a new issue for us.
  17. I believe this used to work for us and stopped working recently. When two Windows computers (servers in our case) sync files, Resilio/BTSync does not manage Windows permissions (ACL) - nor does it do so on other platforms. Therefore, the file should be created or updated/replaced with permissions inherited from the parent folder, not with its own unique permissions. What we are finding is that at least on the server local to me, any file created on the other side comes with a changed set of permissions. A bunch of key entries get dropped (but not all). Even if the file is created on our side, as soon as someone changes it on the other side, the change comes back with the lost permissions. Anyone seen this? Any ideas?
  18. @PwrSrg If you don't want to deal with placeholders don't use selective sync or use 'Remove from all devices' context menu option.
  19. Hello all, The situation i'm not certain about is a Linux pc with a remote share (SMB or NFS) mounted at, e.g., "/mnt/syncfolder/". This folder is synced by a locally running instance of Sync. If mounting the remote share fails in the first place or the share becomes unavailable at some point, the folder "/mnt/syncfolder/" still exists, but the contents will be different since it is no longer backed by the remote share but by a local disk. Typically the folder would then be empty. How will Sync behave in such a case? Will it somehow detect that the folder is not actually a Sync folder and not use it anymore, and will it resume activity when the share is available again? Will it see the empty folder and tell all other peers to delete everything in it? Will it see that other peers have a valid data structure and sync their data into "/mnt/syncfolder/" while it points to some local drive instead of the remote share? Thank you, Henner
  20. Did this ever get figured out? I have the same issue, and can't stand having to constantly remember to go back and search and delete all *.rsls files every time I make significant changes to my local copy. As the original user asked, "How do i stop this from happening?" Thank you.
  21. Did you try to set Sync on pause? You can do it globally or per folder.
  22. I do that at every suitable opportunity, e.g. in any forums, e.g. https://www.synology-forum.de since it is my belief that Resilio is a class of software. By comparison, Syncthing had a lot of trouble just as well until recently. Meanwhile I see there only small differences in the operation and handling. But from the process security these are now equivalent. I think the main problem here is more in support than the feeling that you are in good hands. The software may have quirks, the user usually pull in their rectification without further notice, if you have the feeling that a care takes place. There are enough other examples besides Syncthing, such as ownCloud and the very popular nextCloud in community circles. These too are not perfect, but have the community and their fans who support as well.
  23. That's great news, thank you Alex!
  24. @Maniac You are right! We will turn off logging of ShellExtIO.log by default in the next release.
  25. Earlier
  26. Please take advantage of the new iOS 13's background processing task APIs to do periodic photos backups when the device is idle and connected to the charger.
  27. Instead of asking too many questions if Resilio is alive or dead, we advertise this project! The more users use, the more we guarantee the life of this company! Share Resilio on your social! 👍
  28. Thanks, but that doesn't really help the situation: 1. This was killing my PC's performance, unbeknownst to me. I had to spend hours of research to figure out what was wrong. This option should NOT be enabled by default. 2. This should be a more prominent setting. A registry change should not be required. I'll be setting that key though, thanks.
  1. Load more activity