xfelix

Then don't use https to connect resilio webui.

Synology NAS user. Seems like upgrade from previous verion to 2.7.1, the webui port remain same, not changed to 28889. Probably the previous config file override the default change. Haven't tested to remove resiliosync for a brand new install. Although on Synology firewall i can see a new entry for resiliosync.

So the main issue right now is the predefined hosts entry is not persistent. The host will disappear after put Sync app into background for a while or quit Sync app. If I turn off relay server and tracker server, it will never sync.

iOS app 2.6.4 was just pushed out on AppStore today. the previous version is 2.6.3 which was one year ago.

Resilio Sync mobile used to work fine on iOS. Today I upgraded Resilio Sync to 2.6.4 then all the issues come out. 1. file share / copy file to sync no longer work. It supposed to popup a menu asking which folder in Sync I should choose to store the file. But on 2.6.4, nothing happens. 2. I tried to delete Sync app and download the latest 2.6.4 from appstore again. The copy file to sync issue is gone. But new issue is I have to manually add all shared folder because it is a brand new install now. After enter the share key and name the folder, it does not sync! I go to 'advance' to put predefined host, it starts to sync. But after a while, eg lock screen or quit background, the 'predefined host' entry becomes empty, it still not sync. This app becomes totally useless on 2.6.4. With my very little experience with iOS, this app may have some file permission issue. Especially on iOS 13. My iphone 8 plus is running latest iOS 13.3.1. No issue with Resilio Sync mobile app before 2.6.4. Right now I have no way to downgrade to previous version. I've also submit in app support report to you. Would you please fix this issue? Alternatively, can you pull off this buggy 2.6.4 from appstore so that people can download previous version. Thanks.

Resilio Sync 2.6.2 on Synology NAS has the bug of 2GB file limitation. Downgrade to 2.6.1 or upgrade to 2.6.4 (i haven't tried 2.6.4 yet).

i doubt this ios app will be updated since 2.6.3 has been there almost 1 year.

@Egon Heuson, eg. the latest download is https://download-cdn.resilio.com/2.6.3/Synology/resiliosync_88f6281_2.6.3-1.spk, just change 2.6.3 to 2.6.1.

The problem Nas is DS112 which only has 256MB ram I believe. The one I am running docker is DS216+ii which upgraded ram to 8GB.

I use Resilio Sync Synology pack on an old NAS. 2.6.3 has severe load issue which cause whole NAS extremely slow response. Very high CPU, Mem, and Disk usage. I downgraded to 2.6.2 but has 2G file transfer limit issue. So I have to stay on 2.6.1 by now. I have another Synology nas which can run Docker. No issue of 2.6.3 in container environment.

after almost one month i still haven't seen a clear answer for the issue of 2.6.2 on Synology nas. Is it safe to install the 2.6.2 package on Synology NAS or leave it as 2.6.1? I am using an old model of Synology nas which does not support docker. That's why I ask this question. Thanks.

@sauvagii not sure what tool you use to edit photos. If you use lightroom or similar app, why not store the raw images and editing configurations on the Synology NAS directly, then create a schedule backup from Synology NAS to WD NAS? Your desktop PC is just an interface to use those photo editor applications (mount a folder of Synology NAS).

I believe 18 serial was just released. It's quite new. At least you can use Docker to run resilio in Ubuntu.

You need to be patient. Just wait. It will eventually load the folder info after couple minutes. All depends the amount of data you sync and complexity of the folders. It needs to load everything into memory then display the WebUI. That's how ResilioSync webui designed. Because Synology NAS usually does not have big RAM. Sometimes it takes half hour or longer. You may also try to pause/disconnect some big sync folders through command line. Then try the Webui. Good Luck.

run resiliosync in docker or manage the user ( rslsync ) privilege in share folders.

just manual install the package you downloaded. Click all 'next'. It will detect the existing old one and update it. Please note the user account for ResilisoSync has been changed from 'admin' to 'rslsync', need to make sure the folders permission for the new user.

you can create a github account, fork that official one and modify the version number to 2.5.5 (no coding skill needed). Then create an auto-build repo on docker hub so that you can create a docker image by your own with the latest resiliosync.

i agree. i have to set ram limit for the docker container that runs ResilioSync otherwise it will eat up all the host RAM. On a resources limited NAS, it will take ages to open the ResilioSync webui because of not enough RAM. If dev can find ways to improve the memory efficiency, that will be great.

you need change ownership of those sync folders to rslsync user account. if your synology nas supports docker, strong recommend to use resiliosync docker container instead of package. Just mount the sync folders and no longer have the permission issues.

@Helen Thanks for the help. After reset the peer, no more SyncDiscovery.cpp assert failed error. However, after using 2.5.5 couple days, i noticed a different assert failed error message. What this means? Thanks. "assert failed /home/jenkins/slave-root/workspace/Build-Sync-Manually/bittorent.cpp:846"or 891

@Helen for me, none of my folders have 'use predefined hosts' checked. But still have the same error message as OP.

Same here. No idea what it is. Running 2.5.4 in Synology Docker.

I think i got the answer. There's a sample sync.conf configuration which contains most advanced preferences, even can enforce https on the webgui. Great.

I am using ResilioSync Docker on Synology NAS. I find it not keep the changes of power user preferences settings. Everytime docker container restarts, the settings restore to default. Some settings in preferences will keep, such as speed limit. But other settings like uncheck use upnp port mapping, check update, etc will return to default. Any chance to save these settings to a config file or use docker variables to override the default settings? Thanks.