GreatMarko

Yes, it's already known about - it first arose in 1.4.82 and the devs are currently working on a fix.

Yes, it's a known issue that the devs are in the process of fixing. See the dedicated threads for 1.4.82 and 1.4.83 for more info. UPDATE: This issue has been resolved as of 1.4.93

Ok, and without wanting to sound condescending (as I know you mention this in your original post); but you're definitely running Windows 7, and not say Server 2008? - the reason I ask is because Windows server editions do tend to "block" downloads, resulting in the exact behavior you're seeing, and so you first have to right-click the downloaded file, select "Properties", click the "Unblock" button, and then "Ok" before you can execute the file. This would only be applicable to Windows Server editions though (and in fairness Server 2008 and Windows 7 can look quite similar!)... which is why I'm just double-checking which Windows OS you're running?

As per my earlier response; What Internet Security/Anti Virus software do you have installed? Could that be blocking the Sync installer? Have you ruled that out?

There are others - see this post.

What's the advanced "log_size" setting currently showing? - This setting controls how large (in MB) sync.log is allowed to get on that device.

What version of Sync were you using prior to 1.4.83?

Not at this time - Sync is a completely free product for personal use or non-commercial use within a business environment. However, an "Enterprise" edition of Sync is currently in development, which will likely take the form of some kind paid/subscription offering, and so that could be one way you could support the project financially in the future. On a side note, the developers of some of the various "unofficial" packages for Sync that have been contributed by the community - such as the popular packages for Ubuntu/Debian by forum regular, tuxpoldo - do have ways you can donate to their unofficial Sync projects. Check out their forum signatures for details. Whilst your donation wouldn't be supporting Sync directly, it would be supporting those members of the community who put in a lot of time/work into making their own unofficial packages for Sync available to the Sync community.

You will do!! - it's a known issue - please see my previous post

All, the devs are working on the Sync 1.4/iOS issues

All, the devs are working to adapt Sync for iOS8

Already answered in this thread.

There does appear to be a file locking issue with Office and Sync 1.4 - have a look at this thread also.

You'll never achieve a "100% identical" "mirror/clone" from one server to another using Sync - the reason being that Sync needs to maintain a unique database of files on each device (so it knows what's in sync/what isn't on that particular device, etc) Going back to your original post, it depends precisely what you're trying to "mirror" between servers? If it's just websites, then you could simply add you "/wwwroot" or "/htdocs" folder (as appropriate) to Sync, and that will then sync everything within that to your other server - including sub folders (everything, that is, that's accessible - i.e. not open/locked/in use by other processes). However, as sjoerd points out, this will only sync physical files/folders - it won't "mirror" MySQL databases, etc

No, Sync won't automatically create folders on your second server, UNLESS they're within a folder you're already syncing. Example 1: You're already syncing a folder named "A" between two servers. On one device, you add a new folder named "B" within folder "A" - this will propagate to the other device Example 2: You're already syncing a folder named "A" between two servers. On one device, you add a new folder named "B" outside of folder "A", and add this new folder to Sync on that device - the folder will not be automatically created/added to Sync on your other device

Files in .sync\archive are stored for a period of 30 days, by default. You can change the number of days files are stored for before being automatically removed, by modifying the advanced "sync_trash_ttl" setting. Setting this to a value of "0" will mean that files will never be automatically removed from .sync\archive.

Search for the term "nested", and you'll come across this post from last week: "Nested folders (share in a share) are allowed only when both have RW access"

Yes, it's a bug. Yes, it's known about The current workaround would be to start Sync with a config file, and specify a listening port there.

See Introducing Sync 1.4

The "point" and ultimate aim of the new interface is to make Sync more easily maintainable, portable, and uniform across various operating systems. From BitTorrent: "the web UI gives designers the flexibility to make superficial changes quickly and easily without having to make changes to the application code itself" So, whilst you may not have seen user requests for "a new shiny gui", there are plenty of requests for support on various other operating systems not presently supported (i.e. Firefox OS, Chrome OS, etc). Having an HTML/web based UI means that should other OS's go on to be supported, the UI can be easily ported across.

Peer Approval itself is already available in desktop versions of Sync 1.4:

If you don't use the link sharing feature (and only share keys directly), you can continue to change the device name. Once you generate/share a link, the device name becomes fixed.

You are aware, right, that ".SyncIgnore" has become ".sync\IgnoreList" for 1.4? If you're still adding exclusion rules to ".SyncIgnore", they won't have any affect in 1.4

Auto-Update IS working, it's just that not every new build gets pushed via auto-update whilst Sync remains in beta. From the Unofficial FAQ: "Note: If you currently use the auto-update feature of BitTorrent Sync, it may inform you that your "Client version is up to date" despite a newer build being available. This is intentional whilst Sync remains in "beta" - new builds are currently announced here in the forums in the first instance. Not every "beta" build is pushed via auto-update, only those considered significant/more stable. Even then these may not be pushed out to existing users via auto update until several days/weeks after they are first announced on the forums"

Is the installer actually producing an error, or just not starting? If it's the latter, here are some things to check/try: 1) Check that Sync isn't already running 2) Check that you've fully downloaded the installer (might be worth clearing your browser cache, and re-downloading) 3) Check the installer isn't being blocked by any Anti Virus software you may be running