RomanZ

Discussion continues in existing topic.

Jim, From technical POV both NASes can manage the amount of files with 8 gigs of RAM. It's harder to say about CPU power as it just affects the speed of initial indexing, consequent indices and transfer latency. It's hard to say if that is enough without knowing your demands to the whole system performance and without direct testing.

@Jim_Lafleur It depends on hardware a lot. Large amount of files demands lots of RAM (for instance, 1M of files wil take from 1 to 3Gb of RAM, or DSM will drown in swap). Large volume of data requires strong CPU (otherwise, files scan will take ages). We've got users who sync more than 3M of files and more than 10Tb of data.

1-bay WD is not supported. Synology should work fine, though note that Sync running on low-profile devices will lose significant part of its performance if you attempt to sync lots of files.

In April of 2016 (9 months ago), while Sync was still owned and managed by BitTorrent Inc., BitTorrent’s user forums were hacked and a list of email accounts was stolen. Sync user forums were separated from BitTorrent’s forums and are now managed by Resilio, Inc. We are doing our best to ensure the security of our users, and we are not aware of any new security breaches.

@jjaime Looks really nice instruction. Although, I wonder why have you decide to choose a plain binary placement installation, rather than using our debian package?

@pete harrison Will you share more details? What exactly have you done? Step-by-step description and screenshots are welcomed.

@Biggs The only way Sync relates to torrents is the common protocol. I.e. Sync operates torrents, but these are only your torrents that are created on the fly to deliver your files. Sync does not participate in any sharings done with uTorrent or BitTorrent applications. I guess that your provider uses some simple protocol detection which identified Sync as "uTorrent" and want you to shut it down. Other option is that you get some unwanted guest on your VPS server :). Did you check what is the process communicating over port 35713?

@Animosity022 I'm a bit puzzled on what do you try to achieve with this reverse proxy config? Could you please elaborate? Also, let me know the rolse of Sync here.

@Blubern 1) Set the "enable_journaling" power option to false. 2) Uncheck the "Store deleted files in archive" option. #1 should be done for each instance, #2 should be done for each folder of each instance. It's up to you to decide which folders and which instances you want to keep journals and archives.

@tbo64 You can attempt to install pure x64 build. If it does not help - contact our support.

Hi Edward, Sync for NASes does not support separate users out-of-the-box. Therefore, you either have to share same Sync (you can use your Pro account), or you'll need to launch manually 2nd Sync instance on your NAS.

I see several solutions to this task, each has its own cons and pros: 1. Buy API key. Having API key, you can add folders via API on your NAS and order to download files immediately. PROs: flexibility. Having API you can control almost everything on in Sync on your NAS. CONs: additional cost for API, API only works with Keys, not with links so you need secure channel to get keys from your clients. 2. Use shellscript to start new instance of Sync for each folder you receive. Start each new instance with separate config file, which has folder pre-configured. PROs: no additional costs as in API keys, easy to implement. CONs: configs only work with Keys, not with links. 3. Run separate instance for each customer. Link instance to each customer's my devices and set default folder behavior as "Synced" on NAS. All the folders your customers add will automatically arrive to appropriate instance and sync. PROs: highly automated. No additional scripting required CONs: you have to link each instance with every customer. Also, they won't be able to share RO with you, only Owner type of access. We can't recommend any particular vendor as it might look as advertising. I hope community will share their experience. For the HW configuration of the NAS - it depends on amount of files and folders synchronized, as well as amount of peers planned. Here are some approximate guidelines: 1) RAM. The more files you sync, the more memory demanded. As a rule of thumb, count for 1.5-2Kb of data per file/folder (no matter of the file size). Also note, that some RAM space is always consumed by OS itself, so "256MB RAM" in specification doesn't mead that you get 256MB for the apps running on NAS. If no enough RAM, Sync will swap a lot, losing performance of files delivery. 2) CPU. The more data you get, the longer initial indexing will last. No precise numbers here. The more peers connect, the more CPU load is to keep encrypted connections. If CPU is low-profile, initial indexing will last longer. If many peers connect to low-profile CPU, the data transfer may stop completely as Sync will spend all resources on secure connections maintenance. Hope it helps.

@chadu Could you please elaborate the "I can't see and download the image files from the internet"? Are you attempting to reach files with another Sync instance or with Owncloud? If that is Sync, how do you deploy it to internet? Is that some VPS? Does it sees your NAS4free instance in UI?

@mustha You can update using apt-get or yum (depending on distro) if you are using our official package.

@g3blv As I understand, you ask questions in the context of "what if my key gets stolen". If yes, then: If you are using standard folders - then no, you cant limit to links only. Standard folder is key-based and at the end of day if (say) Eva gets the key, she can reach your content. If you are using advanced folders, it is not a key-based and only can be shared via links. So key can't be stolen and sharing folder thru link requires approval. Although, advanced folder is certificate-based and if someone manages to steal your certificate - it will still be able to get access to your data without any links or approvals. So, this way is more secure as you don't have an ability to transfer vital data (key) over non-secure channel. You can attempt to disable connection to tracker and LAN discovery, and pre-configure your 2 peers with predefined hosts. It requires a bit of networking skills and at least one public IP and control over your NAT to port forward. Although, this smells more like security-thru-obscurity as with this way your protection is just the fact that attacker does not know your public IP and Sync listening port.

@Hans Unfortunately, automatic migration for Asustor NAS package is not planned. We can instruct you on manual migration if you want. That will require some basic Linux skills as it is done via SSH.

1. Both recommended, or at least Android. if you do it only on PC, Android will attempt to send files, but PC will reject to get it. Therefore, if 2nd PC appears, it'll get ignored files. 2. Yes, backup also takes ignorelist into account. Just keep in mind, that if you are doing backup, and removing files from Android, they won't be removed from your PC. Not sure if this is desired behavior for you. You only need Pro if you are going to use selective sync in your setup or if this is commercial / business use. Otherwise, free is enough. Also, you can enable trial PRO on your PC and see if selective sync is something you want.

Hi Roland, Speed depends on many factors. For your LAN I can think of amount of files & average file size, CPU power of peers, HDD load of peers, your network load. 1Mb/sec sounds rather slow for gigabit LAN. In lab environment we get around 100+Mb/sec between 2 peers on top-performance machines. Let's start with this and this articles dedicated to speed improving. Let me know how it goes.

UPD. Logs analysis shows that Sync gets killed by OS due to high memory consumption, which is usually a result of high amount of files and folders.

Ok, cool. Don't hesitate to contact us if you need some help with your package for arch.

@BensTech It's not about config, it's more about QNAP package. It looks like Sync declares itself like app not supporting HTTPS. We'll check if this can be fixed with outr current integration with QTS. Not exactly. Whole Resilio Sync is using 14860. From technical POV BitTorrent Sync is different app, therefore we can't use same port and we have to change to 14860. Current level of app integration with QTS does not allow us to check which option user used to login and enforce the same, though you can SSH to your NAS, manually open sync.conf and put the parameter "force_https" : true inside "webui" section. Don't forget to add necessary commas to follow JSON syntax. By default, Sync WebUI only binds to loopback interface for security reasons. Obviously, we have to override it for NASes.

@bielen2k Could you please try to upgrade your NAS to v2.4.4? There was a fix in 2.4.3 which could help.

@Haider of Sweden Sure, all suggestions stored in this subforum.

Dear community, Resilio Sync 2.4.4 is now officially available. You can get it via direct links below, "Check now" button in app or via official download page. The build is also published to auto-update. UPGRADE Resilio Sync 2.4 is released with Resilio brand, it is treated by OS as new application and will propose you to migrate all your settings from old BitTorrent Sync app (settings are backed up during migration). Please carefully read these articles about updating to Resilio Sync and migration of settings. DOWNGRADE Resilio Sync will make a backup copy of all your settings prior migration into "sync-v2.3.7-1471003319.backup"-like folder (version and timestamp may vary). If you decide to return to 2.3.*, you'll need to manually copy the content to your storage folder, remove Resilio Sync and be aware of next downgrade drawbacks: You'll downgrade to "Free" version and you'll have to re-apply license manually. File association with license files *.btskey is broken so you'll need to apply license in BTSync UI Linking new devices to downgraded Sync is not possible. You'll need to recreate identity if you want to link some new device. Downgrade is not supported for Selective Sync folders (as all placeholder files are renamed to *.rsl*). If you downgrade and your Sync has Selective Sync folders, your files are going to be deleted on all peers. Direct Download Links: Installer for Windows: x86 installer x64 installer Package for OS X: OS X package Gzip archive for Linux: arm armhf i386 x64 glibc23_i386 glibc23_x64 Gzip archive for FreeBSD: i386 x64 Android 2.4.6. A list of what's new, improved, changed, and fixed in this version is available in the change log.