Helen

Administrators
  • Posts

    2,717
  • Joined

  • Last visited

Everything posted by Helen

  1. it shall move out of the archive provided the hashes of files that you will be restoring and of files in the archive are still matching, - if the files didn't change which actually can happen. For example, if files timestamps changed after you deleted them and restored , that would be considered a changed file. Try on a bunch of files first to see. . You might track it in logs on encrypted node, search for lines like "Found file with hash blah-blah in trash..." or alike, sorry, don't remember by heart.
  2. you cannot manage bandwidth from the config file. But you can force some settings and advanced parameters in the config. They won't be hidden from UI, but at least users won't be able to change them. Config file is if higher priority than UI https://help.resilio.com/hc/en-us/articles/206178884-Running-Sync-in-configuration-mode
  3. you need to either link your new phone to server's identity, or manually copy and send the key/link to backup folder from the phone to server
  4. unfortunately you cannot restore the files from Archive on an encrypted node. Encrypted node - is a read-only node. Since the files are "deleted" on the source peer, the encrypted node cannot change this. See other peculiarities about encrypted folders here https://help.resilio.com/hc/en-us/articles/207370466-Encrypted-folders Disconnecting form an identity only removes Advanced folders from sync. Standard folders remain and continue syncing. Encrypted folder is a standard folder. Therefore it propagated deletion as peers were still connected to each other. To be on safe side, manually remove the shares from Sync before doing something bad with the files.
  5. Sync does not synchronize file permissions. Sync runs as Admin on laptop, right? depending on your current setup, few options are: launch Sync as a user on the laptop manually (or using a script) adjust the permissions and give the use access check owner of the parent directory and inheritance rules. add access to the files /folder on the parenting dir and enable inheritance for all children inside. see if it helps
  6. use backup for that https://help.resilio.com/hc/en-us/articles/204762339-How-to-Back-up-data-Android-only-
  7. use docker logs <container name> to view logs. You might want to redirect the logs to a file. https://docs.docker.com/config/containers/logging/ Also, you can edit the docker file and redirect the logs into a logfile by adding --log "/mnt/path/sync.log as a launch argument
  8. Resilio Sync does not use Log4j2 framework, so it's not affected by the vulnerability.
  9. either decrease folder scan interval or rescan manually. See this guide https://help.resilio.com/hc/en-us/articles/205458185-Setting-how-often-Sync-should-check-for-file-changes-
  10. Hi, You need to use IgnoreList , it's available with Free version as well. https://help.resilio.com/hc/en-us/articles/205458165-Ignoring-files-in-Sync-Ignore-List- As for the memory - sync needs around 2 Kb per entry. Entry - is each file and each subfolder level in its path. Sync keeps this all in RAM. Check Sync's storage and see the size of .db files (database) there - the sum of their sizes will give the RAM consumption. Sync also keeps deleted files in database - i mean the files that once were present in sync shar but were removed after. So the bigger folder tree is, the more files are generated/deleted , the more RAM will be required, https://help.resilio.com/hc/en-us/articles/206664690-Sync-Storage-folder Also see here https://help.resilio.com/hc/en-us/articles/209724663-Out-of-memory
  11. 1. if you don't share the key publicly, others will not get it. 2. if you mean someone might *guess* the key, it was discussed here on forum quite a lot years ago, see this thread, for example. 3. Keys are pre-authorized. Use links to require authorization, simply check the option
  12. it's 'Contact support'. we are Resilio Sync. Product sync . com is a cloud storage, it's not us.
  13. Sync uses self-signed certificate which browsers don't trust. You can proceed or use your own trusted certificate. Here are are a few useful links https://forum.resilio.com/topic/71785-how-do-you-change-the-self-signed-certificate-with-lets-encrypt-on-synology https://forum.resilio.com/topic/73141-installed-resilio-on-synology-ds1520-nas-but-keep-getting-your-connection-is-not-private https://help.resilio.com/hc/en-us/articles/4404757430291-Browser-warning-Your-connection-is-not-private- hope this helps.
  14. this also https://help.resilio.com/hc/en-us/articles/205450655-Can-I-move-or-rename-a-syncing-folder-
  15. Resilio Sync runs on Monterey in the lab. What exactly issues do you experience?
  16. Nik, this is forum community for Resilio Sync, they don't know about Resilio Connect With questions about Connect, please contact support from the management console.
  17. Change it through power user settings -tunnel_protocols On DMS7 Sync storage is in a different place, Synology NAS (DSM 7): /var/packages/resiliosync/target/var see here https://help.resilio.com/hc/en-us/articles/206664690-Sync-Storage-folder
  18. You need to edit the config. Change webui: listen port. If you need to change listening port, it's covered in Sync Help Center https://help.resilio.com/hc/en-us/articles/360014432100-Change-listening-port-on-Synology-
  19. where did you get this link? the correct is here https://help.resilio.com/hc/en-us/articles/206178924-Installing-Sync-package-on-Linux
  20. 2.6.3 is not available, but 2.6.4 is. in those links replace the version number , here, for example: https://download-cdn.resilio.com/2.6.4.1344/Debian/resilio-sync_2.6.4.1344-1_amd64.deb
  21. Dear community, Sync version 2.7.2.1375 is released with some fixes. UPD: This version is available by direct download links below, from resilio.com site or via "Check now". NOTE: due to a known issue auto-update from version 2.7.0 on Windows is not possible. Please, instead download the .exe from site or forum and update manually! Please note possible SmartScreen warning: https://help.resilio.com/hc/en-us/articles/360014486120-Windows-Defender-SmartScreen-blocks-Resilio-Sync-installer Full change log can be found here. Direct Download Links: Installer for Windows: x86 installer x64 installer Package for OS X: OS X package Gzip archive for Linux: arm armhf arm arm64 i386 x64 glibc23_i386 glibc23_x64 Gzip archive for FreeBSD: x64 Deb and rpm: download here Android: arm x86 (if not sure which cpu your device has, use arm)
  22. Dear community, Sync version 2.7.1.1370 is released and goes with the following changes and fixes: - Listening port on Synology is forced to be 28889 - Use OpenSSL library for secure connections - Change date format in Sync tooltip - Fixed crash if there’s a peer with old Sync version in the mesh - Fixed license not loading on start in some cases - Fixed randomizing of listening port on Linux - Still deprecated: support for WindowsServers for Sync Home Free and Pro This version only by direct download links below or from resilio.com site. It was not pushed to for 'Check now" or autoupdate. Please note the SmartScreen warning: https://help.resilio.com/hc/en-us/articles/360014486120-Windows-Defender-SmartScreen-blocks-Resilio-Sync-installer Full change log can be found here. Direct Download Links: Installer for Windows: x86 installer x64 installer Package for OS X: OS X package Gzip archive for Linux: arm armhf arm arm64 i386 x64 glibc23_i386 glibc23_x64 Gzip archive for FreeBSD: x64 Deb and rpm: download here Android: arm x86 (if not sure which cpu your device has, use arm)
  23. still the same - do it thru power user settings. remove shares from sync, disable tracker/relay there. add shares back to Sync. enable tracker and relay for folderA will start using them, while folderB won't
  24. i get it right and folder A in on clientA, folder B is on clientB? you'd better use power-user settings for that - these get applied the moment you add the share Once you use 'folder prefs', and add folder B to Sync, it starts connecting to tracker. Even if you disable tracker after that, it might have managed to communicate client's address to clientA., especially if it's folderA that is shared thru link/key.