Syncplify.me Server! v4.1.2 released

We have just released version 4.1.2 of our Syncplify.me Server! software. This version features the following improvements:

  • Fixed: bug in retrieving the last modification date of files stored in UNC paths (SFTP protocol only)
  • Fixed: bug that prevented WinSCP from asking for confirmation before overwriting a file (SFTP protocol only)

Warning: upgrading to this version from any version prior to 4.0.34 will invalidate your license, so please if you are a customer – before you upgrade – contact us to request a license reset.

Note: if after the update you notice any unexpected behavior in the web interface, just hit Ctrl-F5 in your browser; that will force the browser to reload the page as well as all back-end scripts and update the ones that may have been cached from previous versions of the software.

As usual you can download this new release from our website.

Syncplify.me Server! v4.0.30 released

We have just released version 4.0.30 of our Syncplify.me Server! software. This version features the following improvements:

  • Fixed: bug in the initialization of MongoDB replica sets, which affected only High-Availability (HA) deployments

Note: if after the update you notice any unexpected behavior in the web interface, just hit Ctrl-F5 in your browser; that will force the browser to reload the page as well as all back-end scripts and update the ones that may have been cached from previous versions of the software.

As usual you can download this new release from our website.

Syncplify.me Server! v4.0.28 released

We have just released version 4.0.28 of our Syncplify.me Server! software. This version features the following improvements:

  • Fixed: bug in the DiskAES256 virtual file system (VFS) that caused WinSCP to raise an “Error 4: file-write error”

Note: if after the update you notice any unexpected behavior in the web interface, just hit Ctrl-F5 in your browser; that will force the browser to reload the page as well as all back-end scripts and update the ones that may have been cached from previous versions of the software.

As usual you can download this new release from our website.

Syncplify.me Server! v4.0.20 released

We have just released version 4.0.20 of our Syncplify.me Server! software. This version features the following improvements:

  • Fixed: quotas expressed in KB are now correctly evaluated in KB
  • Fixed: issue with detecting legacy MongoDB on Windows XP, Vista and Server 2003
  • Fixed: orphan socket handle upon failed PORT (active) transfer (which only affected the FTP protocol)

As usual you can download this new release from our website.

Making Syncplify.me Server! work with SSHFS/WebEx

Syncplify.me Server! version: 4.0.19+

SSHFS is a FUSE-based filesystem client for the SSH File Transfer Protocol (SFTP); it’s very common among Linux users to mount SFTP targets as local directories. WebEx is a well-known teamwork collaboration tool by Cisco that uses SSHFS to back-up its data to a remote SFTP server.

Unfortunately, the coupling of SSHFS/WebEx – at the time this article is being written – has at least two problems that can cause serious issues to servers that implement the SFTP protocol and its extensions correctly. Continue reading

Syncplify.me Server! v4.0.17 released

We have just released version 4.0.17 of our Syncplify.me Server! software. This version features the following improvements:

  • Added: new bearer-token authorization mode for the REST API (and updated the help/documentation accordingly)
  • Added: [%USER_DESC%], [%TODAY%] and [%SESS_CUSTDATA%] in VFS base path definition
  • Fixed: bug that prevented JSCH-based clients from downloading files correctly

As usual you can download this new release from our website.

Syncplify.me Server! v4.0.16 released

We have just released version 4.0.16 of our Syncplify.me Server! software. This version features the following improvements:

  • Added: compound percentage index to improve Protector™
  • Improved: directory listings now feature attribute-placeholders for virtual directories
  • Improved: better checking of target syntax for all VFS types
  • Fixed: bug in the scripting framework that prevented scripted wildcard (catch-all) user authentication
  • Fixed: DiskAES256 VFS encryption-key change is now (correctly) disabled
  • Fixed: various glitches in the web interface

Note: we skipped version 4.0.15 as we used such build number internally for some laboratory tests.

As usual you can download this new release from our website.

Syncplify.me Server! v4.0.14 released

We have just released version 4.0.14 of our Syncplify.me Server! software. This version features the following improvements:

  • Improved: all services now automatically reconnects to the back-end database if connection is lost
  • Fixed a stability issue in the SuperAdmin dashboard page
  • Fixed a bug in the V3->V4 converter for more reliable upgrades

As usual you can download this new release from our website.

Syncplify.me Server! v4.0.13 released

We have just released version 4.0.13 of our Syncplify.me Server! software. This version features the following improvements:

  • Fixed a bug in the DiskAES256 encrypted Virtual File System (VFS) – this bug prevented files from being correctly downloaded if the client requested odd-sized or unaligned buffers

Very important: to fix this bug we had to change the way we encrypt files at-rest via DiskAES256 VFS; so if you use this particular type of VFS, please, make sure you download all your files to a non-encrypted location before you update to 4.0.13, after the update please delete all files from the location that was protected by the DiskAES256 VFS and re-upload them all. We sincerely apologize for the hassle.

As usual you can download this new release from our website.

Syncplify.me Server! v4.0.6 released

We have just released version 4.0.6 of our Syncplify.me Server! software. This version features the following improvements:

  • Two distinct PCI-compliant configurations to prevent backward compatibility issues
  • Better support for Internet Explorer (still not the recommended browser though)
  • Fixed an issue with self-signed X.509 certificate serial numbers

As usual you can download this new release from our website.