RomanZ

@sirio81 Sync uses different port on every instance (just random, generated on first Sync start). So the most straightforward way would be to monitor it from your network. If you don't want to play with sniffer or any other tools - you can take a peek into sync.log on your PC which contacts with your iOS device and search for iOS local IP. Port would be somewhere next to it.

@kvv213 If someone gets full access to your Sync installation - he still can get to the keys. If not via .SyncUser folder, then via sync.dat file (which also contains full info about your shares). It's a matter of OS to protect data on HDD. Answering your questions: a. Just move it. It is regular Sync folder so you can move it around and Sync will follow. Exception is different partition (Sync uses folder ID to keep track of it, so moving to another partition is kind of delete-and-create action which Sync can't track). If you are not sure - just back up your whole storage folder prior moving it. b. Files and folder names there are pretty much self-descriptive. .SyncUser<timestamp> is your My Devices folder which contains full information about your folders, devices, notifications - everything that is tied to identity rather than to your Sync instance or any of folders.

@FlashPan Yes, you can do it. Uninstall Sync (it will ask during uninstall if you want to wipe out Sync's data... well, you definitely want to keep it ). Install 64-bit version. Run it, it should pick up all the settings from 32bit.

@uytemaf You are welcome! Hopefully we'll get back to single-package-per-architecture scheme in future.

@Carlogubi Well, you need not a generic x86 package. DS415play has evansport architecture, therefore you need evansport package for your NAS. Try it and let me know if it works.

@kamborio Your issue looks very similar to one we are hunting down now :). Unfortunately, no success in reproduction in lab. I wonder if you are okay to supply me with logs? Only affected computer would be enough.

@kamborio Yes. Sometimes, OS splits the event of file movements into "file deleted here" + "file appears here" couple of events. If they arrive separately, Sync could already move file to archive. Starting from 2.x (don't remember precise build) Sync also keeps track of Archived files MD5s and drags file out of archive if MD5 matches. @The Dave Versions 2.3.0..2.3.3 have an issue with saving data. It was possible to start saving data before it was completely loaded. 2 most common use cases: - User closes Sync too early (and Sync has lots of folders to load) - Auto-update dialog closes Sync too early As you can see, it is more tied to version you update from, rather than with version you upgrade to. So, if you have 2.3.3 not matter which version you upgrade to, it still may happen and its better to backup your storage folder prior upgrading. Once you are upgraded to (say) 2.3.5, this client should not longer be affected on later upgrades.

@fix00 No, it can't be rebuild. Consider it has a piece of key for every file and folder, while second piece is RW or RO key. Killing DB kills one piece of key and files recovery becomes impossible. Under "files database" I actually meant whole storage folder. Technically, keeping *.db and *.dat would be enough, but I never experimented in such way. In lab I always transferred whole storage folder which makes transfer from one VPS to another kind of "transparent" to your encrypted peer.

@kamborio Thanks for reporting - we'll try to reproduce and fix. What about your memleak?

@joeritchi Yes, you can just paste the link and mention your nickname (there are several community members on the thread) - supplying logs for the affected peer is also necessary for initial analysis. Thanks!

@bisente Thanks for the feedback. Although, I've got confirmation from several community members in certain cases admin account gets disabled during upgrade even if it has password setup. No warning shown to end user.

@fix00 Your steps are okay, except where you migrate VPS1 to VPS2. The truth is that files are encrypted, and to calculate decryption key Sync needs 2 pieces of information: RO or RW key (encrypted won't fit here, obviously) Files database from encrypted peer. So, when you migrate from VPS1 to VPS2 you also need to: Ensure that you copy not only your encrypted files, but also storage folder. Place Synced folders with exactly same paths they were on VPS1 Run Sync in a way it picks up old storage folder. In this case, Sync on VPS2 is going to seed your encrypted data as you expect.

@Brian Shaw @pm .Conflict files and folders usually appear when filename is mapped into existing another file, which is different though. The most common occurrence for latest version is incorrectly encoded UTF which contains composable characters (like, letters with diacritic signs). I wonder if you guys have any non-latin characters in affected folders?

Hi all. It's a cosmetic bug. The "Destination folder not empty" message should only appear when you receive a link or key and order Sync to store data you are going to receive in non-empty folder. The message idea is to warn you that the data arriving will be merged with one in folder you select automatically. Therefore, some of your files in destination folder could be overwritten. Thanks for reporting. @PaulU With great pleasure. See above... and below . Don't hesitate to ask if something is still unclear. @nunocalaim It's peer-to-peer network. So, every source is a bit destination, too. If you add the same key on other peer, Sync may deliver files to something you consider to be "source". @fix00 Yes, it is possible - if you still have RW/RO key. For example, you've got a PC with RW key and VPS with Enc key. Data is synced fully to VPS. Now your PC crashes and wipes out all data (keep calm, its just a sample ). To get data restored from Enc peer, you need to get any other computer, install Sync and put the RW or RO data there. VPS will start seeding data and populate empty folder on new computer. @ivarson Encrypted folders require significantly more resources than regular ones (even if you actually don't use the Enc secret, just RW and RO) - therefore we want user to understand what he is doing and don't want to make all folders "Encrypted" by default.

@kamborio Oh yes, I do remember :D. For the future time - well, its a tricky thing. It is pretty much the same for all platforms. Sync doesn't work well with future mtime, and there is no simple solution for that issue. Ideally, we'd like to show error message in future so user will be aware of the issue and fix it in his preferred way.

@kamborio For the moment (=2.3.6) we've addressed all known leaks. Will be happy to get your logs :). As this is leak, only one peer (which is leaking) would be enough.

@uytemaf I've responded in another topic, so closing this one.

@Bob_Collins We've got reports that Sync does not work on bromolow and avoton architectures under DSM6 control (though we don't know reasons at the moment and working to find it out). These platforms are also x64. I suspect that it might affect cedarview as well, though no confirmation for now.

@uninexus Ideally, should work out of the box. Get package and install it. Although, we've got reports that something goes wrong with Sync on DSM6 on avoton architecture. If you are willing to debug what happens on your NAS - give us a mail (mention this forum topic) and we'll guide you thru debugging process.

Dear community, Sync 2.3.6 is now available. You can get it via direct links below, via official download page or via "Check now" button. Build is not yet available via auto-update. 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 A list of what's new, improved, changed, and fixed in this version is available in the change log. Latest Android build is now also available via direct link: 2.3.5 APK Latest Raspberry Pi package is available via direct link: 2.3.6 DEB Known issues and peculiarities: - Linux users please note: starting from 2.3.0, Sync now creates and uses storage folder (.sync folder) in current directory, not next to binary - Upgrading from 2.3.0-2.3.3 may remove your identity and folders. It is strongly advised that you backup your storage folder prior to upgrade to 2.3.6.

@joeritchi It looks like we've found the root cause of @KawateTadako's issue. PM me if you are willing to try possible fix.

@Carlogubi @Acumen @uytemaf I suggest taking a look at our KB article dedicated to Synology NAS, it contains better workaround than downgrading to 2.2.7. In short, you need to get the ARMHF binary and replace it for ARMADA* architectures We plan to support DSM6.0 of course and are working with Synology engineers to get compatibility issues resolved. I can't claim ETA for now as resolution depends not only on Sync Team.

@flypenguin -> @joeyvandijk Admin account gets disabled on DSM6.0 only if your pass is empty. @TinMan This sounds to be different issue. Avoton uses x64 CPU, not ARM and should be working fine. If you are willing to help us getting this issue resolved - mail me, note this topic in message body.

@citronbleu It directly depends on amount of files you attempt to Sync. If you'll try to sync 1M of files, Sync will hog your RPI rather quickly. RPIv1 has only 512Mb, so that would be enough for around 300K of files - if you leave no space for other apps in RAM

@goldsmit409 Just use a regular trial license. It allows all pro features. For the API - there is special license, apply for it here. If product fits you - you'll need business license. For the monitoring - there is no tool to monitor. Some information about remote peer is going to be visible on the server which is going to seed data to your travelling servers. If you want to get some management server - I suggest looking into Sync IT product.