Release Notes

3.0.0

• New transfer engine. Transfers run over QUIC on UDP, and every transfer is encrypted with TLS 1.3.

• Added a choice of UDP or TCP transfers. By default, TCP transfers share the API port.

• Transfers now resume after a dropped connection or a receiver restart, also when uploading to S3.

• Added browser downloads for web shares. The web share tier can serve TLS itself, and an archive download can resume.

• A receiver behind a NAT or a firewall can now receive transfers without an open port. The receiver connects out to the sender, or to a relay.

• Transfers now run at the same time, up to --max-concurrent-transfers (default 10), and one at a time to each destination by default. Urgency decides which transfer runs first.

• S3 files can now be up to 5 TiB. Every S3 write is verified against the ETag the store returns.

• Supported server platforms are Linux (Ubuntu 22.04, Rocky Linux 9) and macOS. The macOS server runs on Intel and Apple silicon.

• Removed the --transfer-min-cipher option. Transfers are always encrypted.

• Removed options that no longer have an effect, including --recv-nat-traversal, --disable-port-multiplex and --recv-relay-multiplex. Remove them from the server’s response file before you upgrade.

• A 3.0.0 server does not transfer to or from servers and clients older than 3.0.0.

• Fixed a resumed transfer that stopped making progress when its manifest held many files. The receiver now tells the sender that it is still reading the manifest, so the sender waits for it instead of retrying. The sender waits for at most 15 minutes. Both servers need this build.

• Various bug fixes.

2.9.6

• Fixed an issue which caused transfers larger than 1 TB to report an incorrect total size.

• Fixed an issue which caused an in-progress transfer to lose progress when a receiver restarted twice in quick succession.

• Fixed an issue which caused queued transfers to wait indefinitely when the destination became unavailable. These transfers now report an error instead.

• Fixed an issue which prevented deleting a stalled transfer without restarting the server.

• Various bug fixes.

2.9.5

• Added the ability to save Watch Folder snapshots automatically at the end of a transfer.

• Added separate sandboxName input parameter for improved configuration flexibility.

• Extended retention of expired shared link tokens to 30 days (previously 48 hours).

• Allow updating shared link expiry dates to a date earlier than the current date.

• Various bug fixes.

2.9.4

• Added support for Ubuntu 22.04 LTS.

• Added support for Rocky Linux 9.2.

• Added additional logging for network timeouts.

• Various bug fixes.

2.9.3

• Added support for Concurrent Transfers (Beta).

• Added UDP transfer port to transfer logging.

• Added the ability for Watch Folders to detect if a Connected Folder has been disconnected.

• Increased default cache size from 2GB to 4GB.

• Fixed an issue that caused some integrity checks to fail when uploading to Wasabi.

• Various bug fixes.

2.9.2

• Added a feature to prevent unnecessary logging of repetitive SSL errors.

• Added support for incoming transfer status.

• Improved loading time of large directories.

• Various bug fixes.

2.9.1

• Added support for transfers to a client API end-point.

• Improved incoming transfers functionality.

2.9.0

• Added support for M1.

• Added support for Windows 11.

2.8.3

• Added support for incoming transfers.

• Increased frequency of timeouts from 10 seconds to 60 seconds.

2.8.2

• Added option to skip file errors caused by moved or deleted files during transfer.

• Added cloud transaction retry in server startup configuration.

• Improved process owner authentication for localhost API connection.

• When host service stops, transfer automatically resume from the last checkpoint.

• Various bug fixes.

2.8.1

• Improved watch folder usability and bug fixes.

2.8.0

• Added watch folder feature.

2.7.2

• Improved multithreaded write engine.

• Improved server memory usage.

• Fixed S3 uploads hanging at transferring large amount of files.

2.7.1

• Improved receiver file writing performance using multithreaded io.

• Fixed an issue with persistent directory path at installation on Windows machine.

• Added Win10 application level awareness of long file path.

2.6.5

• Optimized domain user sandbox resolution

• Added long file path support on Windows

• Various bug fixes.

2.6.4

• Increased the speed of sandboxing files.

• Optimized transfer processing.

• Added safer serialization to persistent state files.

• Bug fixes.

2.6.3

• Fixed a timeout when resolving many sandboxed files.

2.6.2

• Added --cloud-cache-file to allow a larger page file for use with S3 uploads.

• Added --send-host to restrict outgoing transfers to a specific interface.

• Added --default-file-driver which allows selecting the backend file driver.

• Internal optimizations when dealing with S3.

• Various bug fixes.

2.6.1

• No Server Changes

2.6.0

• Renamed --max-file-cache-size, --max-file-cache-download-size, --max-file-cache-upload-size options to --max-cloud-cache-size, --max-cloud-cache-download-size, --max-cloud-cache-upload-size.

• Fix bugs with S3 multipart uploads.

• Added ability to change description and expiry dates of tokens.

• Added ability to remove the license from a licensed server.

2.5.3

• No Server Changes

2.5.2

• Fixed bug where out of order packets could be rejected.

2.5.1

• Added fallback file IO method for avidFS.

• Added recv.transferStarted trigger.

2.5.0

• Added new wrangler permission and functions.

• API tokens can now successfully make download tokens.

• Various bug fixes.

2.4.0

• Added support for API tokens.

• Added fine grained permissions.

• Fix bug where S3 file containing certain special characters could not be downloaded.

• Command-line API interface returns better error codes on failure.

• Added --api-disable-api-tokens option.

• Various bug fixes.

2.3.1

• Fixed bug where SMB shares on Windows might not authenticate correctly.

• Fixed bug where the server would not run on macOS versions older than 10.12.

2.3.0

• Added support for maintaining timestamps and only writing if the source file is newer into the API.

• Failed transfers will now attempt to tell the receiver to clean up any part files.

• Added new recv.transferComplete.json trigger which uses a JSON payload that include the transfer’s user data. Note that the user data must be specified during createTransfer; any user data added afterwards will not be part of the trigger payload.

2.2.1

• Documentation update. No Server Changes

2.2.0

• Added support for additional transfer ciphers including AES 256. Default remains AES 128.

• Added --transfer-min-cipher option.

• Fix bug when truncating a file while it’s in use.

2.1.0

• Added API support for setting the server license.

• Improved error messages for invalid licenses.

• Added standard administrator groups as supergroups by default.

• Set the maximum number of open file handles on macOS.

• Bug fixes.

• Changed minimum support version of Ubuntu to 18.04.

2.0.2

• Fix bug with file renames.

2.0.1

• Documentation update. No Server Changes

2.0.0

• Changed to a new licensing system.

• Brand name changes.

• Updated third-party SDKs.

• Added --trigger-log option.

• Added --trigger-on-api option. Note that this changes the default trigger behaviour.

• Server does not try to access the network instantly at startup if it’s not yet ready.

• Set the maximum number of open file handles on Linux.

• Bug fixes.

• Removed support for CentOS 6.