Gane O'dwyer

Unfortunately no. The only thing if you create a new folder that will contain the same content and send it from B->C.

But it impossible to use the same porst fro all Sync instances that will run in the same time on your device.

Run Sync with config and edit there WebUI settings prior to app start. Also the simpliest way this one ( using --webui flag): --webui.listen <IP>:<port> Set the webui listening interface. By default, web UI listens only on 127.0.0.1 interface for security reasons. This can be changed with the following command: --webui.listen <Interface_IP>:<port>, for example: ./rslsync --webui.listen 0.0.0.0:8888

@BensTech I saw that you have the active coversation with support team. Let's discuss the issue with them.

Yes, still in active development.

This is a common difference between folder types. Just try to add a standard folder instead of advanced.

Have you checked the app version from the Sync WebUI? If no, just launch Sync and check the current version of course after the app upgrade.

Very interesting case. What will happen if you restart Sync? And are these files with zero size really corrupted of they could be opened?

If you're syncing your files using advanced folders, then in this case, transfer speed can be smaller than transfer speed for standard folders because of using the SSL encrypting.

@PhilTone You have a folder on the NAS with selective sync option enabled. As there is no integration with OS you can observe placeholders in Sync WebUI only. To get them synced simply download them manually or disable selective sync option. To get file from the remote node you need at least 2 peers online and of course once of them have to have files with real size otherwise you are were not be able to download it from the remote peer that also has placeholders. If you peers do not see each other please do pay attention on that web page->https://help.resilio.com/hc/en-us/articles/205450205-Peers-aren-t-connecting

Thank you for your efforts.

RO peers can only read data in a shared folder, therefore if you update (add, delete or modify) files on RO peers, these changes will not be synced to others. So if I am right this is your case.

@fefrie Files are synchronizing step-by-step and piece by piece. The more peers you have the fastest files would be synced. But as for now there a limit to the number of torrents that can be in work at a moment. It means 100 simultaneous torrents for Sync transfer.

If something happen on the RW peer that changes will be send to all remote nodes. Any changes on RO peer will never influence the remote nodes.

@auitj Please do make sure that you have installed the most recent app version that is 2.5.12. We do not option to save current config but if you like you can write a script that will allows you to save a stoarge folder of the app to the new storage path.

It means that the app wasn't installed correctly. Please do contact support to get further steps.

In this case contact support and agree to attach logs, write down the time when Sync was not running in the background but should. Also please do check in the Android processes if the Sync service running.

Resilio Sync will not permit you to sync one folder location on your computer to another location on the same computer according to app design.

Do you have any task-killers installed or optimizers?

You can stop Sync file and copy storage folder to another location but do not forget to edit that path in config file then start Sync. Also you can remove .sync log and .journals as their archives.

Hello, of course it will be done. But when a major release with fix will be published unfortunately no ETA .

Unfortunately it is not allowed to sync separate drives on the same device.

The issue is known but not fixes yet. The fix will be added in the major release.

@Jineapple Send me a path to that folder. I can suppose that storage folder of the app includes that directory.

@jbrody Sync doesn't have default backup solution for files syncing and removing without affecting other nodes as Android devices do. This could be achieved only using workaround but not implemented functionality.