bigjohnx Posted September 10, 2014 Report Share Posted September 10, 2014 Many users like me may encounter problem when installing the latest version of btsync app package that coming from spk source: packages.synocommunity.com . The main problem is the user cannot accept the EULA forever and cause the btsync malfunction. After investigation, I found out that the 1.4.x version of btsync in arm / linux platform may have an issue if running btsync with config file that include user and password information and cause the user cannot accept eula, even checked the box. Here is the work out on this issue, hope can help you all: 1. Uninstall the btsync to clean up all app folders;2. Install the btsync from the source : packages.synocommunity.com3. During installation, enter the btsync device name, user and password, then click next4. **Important Step** Uncheck "Run after installation", click Next, then click OK5. Go to Synology control panel to enable SSH if not enabled yet6. Use putty (windows) / ssh (osx/linux) to login your NAS with user root and admin password7. After enter ssh, type the command "su btsync"8. Type the command "vi sync.conf" to edit the file, add "//" to comment the config setting as following sample: { "device_name": "NAS", "storage_path" : "/usr/local/btsync/var", "pid_file" : "/usr/local/btsync/var/syncapp.pid", "webui" : { "listen" : "0.0.0.0:8888" // ,// "login" : "login",// "password" : "password" }} Please remember in the listen line, add the "//" before the "," 9. Type "ZZ" to save the file10. Go to Syno app manager, start / run the package11. Go to web site http://192.168.x.x:8888, enter user name, password x2, check eula12. Try add folder, if you see all the folder, BINGO!13. Additional info: If your NAS only have single volume (most of NAS use this setting), you can add the following setting after "password" line and before "}": (beware need add the "," at start of this line). Restart the btsync app afterward. This setting may help you to pick up the share folder more easily. ,"directory_root" : "/volume1/" That's all.....hope can help you all. Quote Link to comment Share on other sites More sharing options...
RomanZ Posted September 11, 2014 Report Share Posted September 11, 2014 @bigjohnx Thanks for the detailed instruction! It helped to pinpoint the bug. We'll fix it soon. Quote Link to comment Share on other sites More sharing options...
sudowtf Posted September 11, 2014 Report Share Posted September 11, 2014 My only working solution was to remove v1.4, then install v1.3 from http://www.andreasgiemza.de/allgemein/bittorrent-sync-1-3-109-for-synology-nas/ then upgrade to v1.4. Starting with v1.4 and stopping & editing .conf failed for me. Quote Link to comment Share on other sites More sharing options...
bigjohnx Posted September 12, 2014 Author Report Share Posted September 12, 2014 @bigjohnx Thanks for the detailed instruction! It helped to pinpoint the bug. We'll fix it soon.Welcome. Please also notice that same issue occur in arm build also. I tested on WD Mycloud FW 3.x and got the same result and using the same method to resolve the problem. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.