Both the discovery and the sync protocol has changed from v0.11. Devices running v0.12 will not discover or successfully connect to devices running v0.11.
If you run a private discovery server, you must upgrade it to the v0.12 release. The protocol and port number is different, so old and new discovery servers can coexist on the same machine and serve their respective clients.
The API endpoint
/rest/system/discovery has been removed for POST requests.
The default list of discovery servers is no longer explicitly in the configuration - instead the configuration entry “default” represents the full set of default discovery servers. If you need to edit this default set, watch the startup messages for a full list of used servers and edit to suit.
Important Changes and Improvements
Syncthing now has the ability to connect two devices via a relay when there exists no direct path between them (firewalls on both ends). There is a default set of relays that is used out of the box, although private relays can be used and relaying can of course be disabled. Relayed connections are encrypted in the usual manner, end to end, so the relay has no more insight into the connection than any other random eavesdropper on the Internet.
Device Discovery over HTTPS
The global discovery protocol has been rewritten to use HTTPS over the standard port 443. A number of geographically redundant discovery servers have been deployed.
Minor Changes and Improvements
Scanning Progress Indicator
Folders now indicate scanning progress in percent in the same way as while syncing.
Devices can be paused in the GUI, which means they will stay disconnected and consume no data quota or other resources.
Signed Automatic Upgrades
Automatic upgrades are now cryptographically signed and verified before an update is applied. This also goes for manual upgrades à la
syncthing -upgrade-from http://.../syncthing.tar.gz, which is thus a safe way to upgrade to a package of unknown provenance… There is a new CLI utility
stsigtool to manually generate and verify signatures. There is a documentation article on the subject.
Extended Usage Reporting
Syncthing now reports what features are in use (such as Introducer, Master Folder, etc), as well as wether default or custom discovery and relay servers are used, and the number of CPUs in the system. This provides us with guidance about where to focus efforts. As this is a change from the previously reported data set, any previous acceptance of anonymous usage reporting is automatically revoked and the question pose again some time after installation. The exact details of the new report values are here and here.
Relaxed Folder ID Restrictions
Folder IDs used to be limited to a strict subset of ASCII with very few non-word characters, and maximum 64 characters. Ideally, we should have separation between the folder ID and it’s label, but we’re not there yet. However, in v0.12 you can use whatever characters you like, up to 256 bytes. This means accents, special characters, Cyrillic or Asian scripts, and so on.
Debug Output via API
New API methods allow setting the debug flag on all of the existing debug facilities, and getting log output. Actual debug UI to be added.
Syncthing can now connect through a SOCKS5 proxy. Set the environment variable
all_proxy before starting Syncthing, to a URL on the form
socks5://host:port. This may get a cleaner way to configure it with time…
$ export all_proxy=socks5://10.20.30.40:6789