How to Install

To update an existing x360Sync Private Cloud Server installation, simply launch the embedded Updater tool.

To download the new installer manually, please refer to this article: Download the latest Private Cloud Server - x360Sync.

Important Notes

• Windows Server 2012 will soon be no longer supported. Please update your environment to a newer OS version to keep receiving the latest Private Cloud updates. If you'd like to migrate instead, please refer to Migrate the system to a new server - x360Sync
• Private Cloud partners who customize their Web UI need to install node.js 20 LTS to the machine to build the frontend assets (we verified support for version 20, but it might work with 22 as well). Please see https://nodejs.org/en/blog/release/v20.19.6 and https://nodejs.org/en/blog/release/
• When updating from Private Cloud 3.6.10 or earlier, it is required to install Private Cloud 3.6.20 or 3.6.21 first to modify the necessary database fields. After this, Private Cloud 3.6.30 will become available. If you run the Updater tool in the installation folder, it will automatically display the latest available release

New Features

Windows Clients: ARM64 Support

Added support for ARM64 devices (e.g. Microsoft Surface). The installer is universal and automatically selects appropriate components (x64 or ARM64) based on the device architecture.

Thin Client: Cache Limits and Auto-Cleanup

Thin Client now has cache limits and cache auto-cleanup to help users save disk space.

• Files that haven't been accessed for more than 180 days will be removed from cache automatically
• By default, cache size limit is 10% of the disk size, but not less than 5 GB and not more than 100 GB. When the total size of cached files exceeds this limit, the files accessed longest time ago will be removed from cache automatically to keep it within the limit
• Files with sizes exceeding the maximum cache size limit can still be downloaded when opened
• Files that were accessed less than 2 hours ago are never removed automatically
• Files explicitly selected for offline use by clicking "Always keep on this device" don't count towards the cache limit and aren't removed from cache automatically
• User interface to control cache settings might be added in the future. In the meantime, if you need to adjust these settings, open the program folder in Program Files, then navigate to conf folder, open config.ini and add the following lines to the [cassia] section. After saving changes, restart the service or reboot your computer for new settings to take effect.
  • maximum_cache_size_mb = 20480 (in megabytes, not used by default, 20 GB in this example) will set a fixed, non-calculated cache size limit. When added, this will override the three parameters below
  • cache_disk_size_percentage = 10 (in percents, 10% by default) will set the percentage of the disk size to allocate for cache
  • min_cache_size_mb = 5120 (in megabytes, 5 GB by default) will set the minimum possible cache size even if it's more than the percentage specified above
  • max_cache_size_mb = 102400 (in megabytes, 100 GB by default) will set the maximum possible cache size even if it's less than the percentage specified above
  • auto_remove_cached_files_min = 259200 (in minutes, 180 days by default) will set for how long the app will keep the cache for non-accessed files before deleting it automatically

Known limitations: cache auto-cleanup currently doesn't remove partially downloaded cache that could accumulate when you navigate through folders and the operating system requests file thumbnails or other properties. In a future release, we will make such partial cache files smaller to save disk space; we will also include them in auto-cleanup. In the meantime, if you still observe large amounts of space used by cache, you can right-click on the folder representing a root (team share) and choose "Free up space".

For more details, please see Thin Client cache limits and auto-cleanup - x360Sync.

Web: Password-Protected Share Links

Now, when creating or editing a share link, either public or secure, you can add a password to it:
You'll be able to manually type the desired password or generate it automatically. Make sure to copy your password in a safe place before closing the modal window, as it won't be visible once saved.
Only the people with the password will be able to access the share link contents:
If needed, you can disable or change the existing password when editing the share link:

Web: Upload Requests

With upload requests, you can generate a link allowing anyone to upload files to your shares - even anonymously, without having an account and without seeing the contents of those shares. The uploader can be a person outside of your organization, even a person without a guest account. 

To make an upload request, choose the folder where you want files uploaded. It can be any folder in a common team share or in My Files. Then, right-click on it and select Request Upload in the context menu.

On the resulting screen, you will need to enter the upload request Title (visible to the uploader). You can also optionally enter Description (visible to the uploader) and set an Expiration Date after which the link will stop working. You will also be able to review the Upload Destination path.

After clicking Create, you will be presented with the next popup where you can copy the Upload Request URL to share with others. You can also add recipients and an optional message to them. If you choose recipients, the Web portal will send emails with the upload request details and URL to those people after clicking 'OK'.

Unlike with share links, the list of recipients is used only to send out one-time notifications. Recipients are not stored, they are not given any additional permissions.

When a recipient opens the upload request URL, they are presented with a note "John Doe has requested files" and a form asking them to enter their email (unless the recipient is logged in). This email is not validated but can potentially be used for audit purposes.

Next, they will see the upload request Title and Description, and a note to carefully review the files before starting the upload as the recipient won't be able to modify or remove files once uploaded.

The person uploading the files can't access any contents of the folder they are uploading to. They also can't access the files they uploaded. 

For more details on this feature, see: Create and manage upload requests - x360Sync.

Enhancements

Private Cloud

• Removed the file size limit of 1 GB for uploads done using the REST API v2 endpoint in Private Cloud environments
• Python bundled with Private Cloud is upgraded from 3.8 to 3.12 for both fresh installs and updates
• Apache bundled with Private Cloud is updated from 2.4.56 to 2.4.63 for both fresh installs and updates

Server

• Added necessary backend changes to support new Web features
• Improved performance by optimizing the calls retrieving the latest file revisions
• Added necessary prerequisites to improve the speed of restore and deletion processes
• Improved the stability of the wipe process (permanent file deletion)
• Introduced better tracking of inactive root subscriptions. This will allow purging of subscriptions that are inactive for long periods of time to improve backend performance

Thick and Thin Clients

• Significantly improved the initial scan time when adding a new team share, backup or FSE mapping
• Introduced local rsub database integrity checks and auto-repair functionality. Local rsub corruption could cause various synchronization issues, and now the Client will rebuild the database when this problem is detected
• Updated libraries for better performance and reliability

Thick Client

• Added support for Windows Server 2025
• Increased the default value of connection_acquire_timeout from 60 seconds (1 minute) to 300 seconds (5 minutes), enhancing Client reliability when handling especially large roots

Web

• Improved share dialog UI:
  
  • Added tooltips with hints to some of the fields
  • Redesigned "Copy" button and made it clickable when using the "Secure Share" option. This will allow users to easily copy the link and send it to people added in "Recipients" using alternative channels such as work chats
  • Renamed "Allow anonymous users to edit files" checkbox to "Allow anonymous users to edit docs in Web Editor" and moved it to "Share Options" section
  • Simplified email notification parameters to one checkbox "Notify New Recipients"
  • Added a hint when user creates a secure share link, but doesn't add any recipients: "Share has no recipients. Add recipients to provide them access to this content"
• Improved UI/UX for navigation through team shares, folders and files:
  • The name of a team share, folder or a file now turns orange only when hovered over the area where a single click opens it
  • Icons are now also clickable and open the item after a single click, same as names
  • While single-clicking on a folder or a file area outside the icon/name will select it, same as before, double-clicking on the area will now open that item
• Added sorting to the lists of team shares for users and admins. Now they can easily identify the team shares taking most space, having most files or simply use the alphabetical order
  
• Improved confirmation messages when deleting team shares and backups, unlinking machines, removing team share subscribers or disabling sync to team shares. These messages now contain details about the object that is being affected so that admins could double-check their actions before confirming. Some of these messages now also explain the outcome of these actions in a greater detail.
  Some examples:
  
• Added a confirmation message when unlinking a mobile device
  
• Improved file policy checks and warnings in both drag-and-drop and standalone uploaders. Improved progress display in drag-and-drop uploader
• Simplified UI for selecting folders and subfolders for File Server Enablement (FSE) and Backups. When a parent folder is selected (checked) in the folder tree, all its subfolders (and their subfolders) are marked in UI as disabled (grayed out) to let the user understand that they don't need to select each of them. Added a message for clarity: "Note: If you select a parent folder, all its subfolders will be included automatically."
  
• Added support for password protected .pdf files when using Web Viewer
• Added translation of daily digest emails and other UI elements into all supported languages: German, Dutch, French and Portuguese
• Added a missing icon for "Branding" tab in the organization settings
• When an admin adds participants to a share link created by a different user, the email for share link recipients now has this admin's name instead of the original creator's name in email title and body
• Improved the dialog shown to admins when disabling 2FA for a selected account to clearly state what the user will have to do next, depending on whether 2FA is made mandatory for the organization or not
• Removed "email" from the tooltip for "Require two-step authentication" in organization policies as email method is no longer supported
• Security and performance improvements to the Web Preview functionality on both Server and Client sides
• Security improvement: added escaping of HTML input in Share Link message and in Email Users message fields to prevent malicious code from being sent. HTML templates from organization settings still allow entering HTML code
• Implemented more strict rules of OAuth token expiration
• In all cases where a subscription to a root is removed from Web, Web now sends a notification to the Server to reduce the number of RPC calls to be processed by the Server and reduce the Server load
• Improved logging for better troubleshooting
• Improved the dialog for mass file restore:
  Changed the default option from "Restore All Files" to "Restore Files Deleted Between".
  Made it possible to set the same date in "Start Date" and "End Date". Using such parameters will restore all files deleted during these 24 hours in the current user's time zone.
  Added a warning for "Restore All Files" option to help users avoid accidental restores of large volume of unnecessary files deleted long time ago.
  
• Improved the restore progress UI: when the restore is finished, it shows the total number of files that have been restored.
  
• Improved the tracking of the restore progress, where large restore operations taking long time could display timeout errors despite restore still running. If you still observe errors during a long restore, it's best to check activity log first to confirm no new files are being restored (shown as created on Web by the user running the restore) before attempting another restore or contacting Support. We are working to continue improving the restore performance and UI for better user experience
• Improved the snapshot creation UI for admins:
  Added the name of the original team share and the name of the new team share to be made to the confirmation dialog. If the user enables the option "Only Include Data Up To The Following Point In Time", the chosen time is also displayed in the confirmation dialog.
  Additionally, fixed a bug where going from the confirmation dialog back to the parameters and then finally confirming the snapshot operation would try to generate as many snapshots as many times the user saw the confirmation dialog
• Added the ability to edit expired share links to files and folders
• Added a new column "Download Size" to the lists of Team Shares and Backups for administrators. Replaced the old column "Size" with the new column "Download Size" in user's lists. Added tooltips to clarify the difference: old column "Size" displays how much space is counted towards the organization quota (the size of all files compressed, including deleted files and old revisions), while new column "Download Size" displays how much space the team share or a backup will take on the end user device if downloaded in full (the size of all active files when synced down and decompressed).
  
• Added the ability to move files/folders within a shared folder when "can modify" permission is given to a user.
  
• Introduced the minimum allowed period of 7 days for the parameters of auto-erase of files and revisions. This will prevent administrators from using unsafe settings that could lead to unrecoverable data loss in case of accidental deletion.
  
• Increased API token lifetime to 24 hours
• Implemented HTTP Strict Transport Security (HSTS) header, Content-Security-Policy header and Subresource Integrity (SRI) checks for better security
• Introduced various security improvements, including library updates, fixes for CSRF and XSS vulnerabilities, fixes to cookies attributes, etc.
• For security reasons, increased the minimum length of a new password from 8 to 12 characters
• For security reasons, changed how guest users see folders shared with them in their list of Shares. Now, instead of exposing the full path to the shared folder from the root, UI displays only the name of the shared folder itself
• For security reasons, changed how shared folders are mentioned in notification emails for share link recipients. Now, instead of exposing the full path to the shared folder from the root, the email displays only the name of the shared folder itself
• When an organization is disabled by the administrator, the share links made by its users will no longer be available. If the organization is re-enabled, the share links will become accessible again
• When an organization trial expires, the share links made by its users will no longer be available. If the organization is switched to paid or its trial is re-enabled, the share links will become accessible again
• Added RFC2822 compliant Message-ID header for all emails to prevent anti-spam check failures on some services, especially when using a third-party email server
• Slightly improved the texts of welcome emails that are sent automatically during the account creation and triggered by the administrator manually, including the emails sent to AD-integrated accounts
• Improved translations for supported languages
• Introduced better tracking of inactive root subscriptions. This will allow purging of subscriptions that are inactive for long periods of time to improve backend performance
• Improved the error handling and introduced better messaging when a user tries to permanently delete a file while having no purge permissions
• Added enhanced logging to desktop client updater for better troubleshooting
• Added the ability to change the default language, location and region for Web Editor. This affects how dates and numbers are interpreted and shown when editing Office files.
  To change the region, set the proper parameters in config.py for the web application. For example:
  DEFAULT_CWE_LANG = 'en-US' - language code
  DEFAULT_CWE_LOCATION = 'us' - location
  DEFAULT_CWE_REGION = 'en-US' - regional settings
  When using more than one web node, each of them needs to be updated accordingly.
  You can refer to ISO 3166-1 alpha-2 two-letter country codes and ISO 639 two-letter language codes

Fixes

Server

• Added proper error handling and API response for cases when the Client attempts to delete a missing file/folder. Thin Client won't get into a stuck sync state in this scenario anymore
• Fixed a bug where snapshots could fail or not restore certain files from specific dates as expected, because child folders were not deleted inside deleted parent folders
• Fixed a bug where, in some cases, the Server did not handle errors from the get_file_policy call properly, resulting in an increased number of "permission denied" errors in Thin Client
• Fixed a bug introduced earlier in 3.6.x where unaccounted files could appear on the Server disk storage if the Server had a problem creating database records for these files
• Fixed several bugs in connection socket handling that could cause the backend to crash
• Fixed a rare bug where incorrect thread execution could cause the backend to crash

Thick and Thin Clients

• Fixed a bug where the wrong Client version was displayed in status report, service output logs and GUI logs. This will help support with troubleshooting
• Fixed a bug where local root subscription database inconsistency could cause Client to make excessive RPC calls, resulting in increased load on the backend

Thick Client

• Fixed a bug where the Client couldn't sync up a file if its name contained translations of special characters, such as: "file_with_asterisk~12.txt"

Thin Client

• Fixed a bug where Thin Client could attempt to sync root subscriptions that existed locally but were not present in the list received from the Server, resulting in excessive RPC calls and increased load on the backend
• Fixed a bug where periodic scan of FSE/Backup subscription didn't work as expected
• Fixed a bug where synchronization could be failing after moving a file/folder into a folder that hasn't been synced up yet
• Fixed a bug where the wrong Client version was displayed in status report, service output logs and GUI logs. This will help support with troubleshooting
• Fixed a bug where local root subscription database inconsistency could cause Client to make excessive RPC calls, resulting in increased load on the backend
• Fixed a bug where Client was unable to reconnect to the Server properly in some cases, causing permission denied errors and getting into a stuck sync state

Web

• Fixed a bug where the list of machines on admin dashboard would incorrectly show "Agent needs update" next to machines already running the latest version of Thin Client
• Fixed a bug where restore status window would say "Unknown error" or "Pending" when user starts restore, closes the page and reopens it the next day or later. Task results are now stored for 14 days instead of 6 hours
• Fixed a bug where M365 (Office Online) editor would fail to refresh the file lock, causing session timeout error
• Fixed a bug where team share and backup roots of a deleted child organization would remain visible to admins in lists of parent organization roots
• Fixed a bug where deleting an organization via API was not consistent with deleting an organization via Web and could leave behind some accounts, shares, and backups
• Fixed a bug where it was possible to add "." symbol to the beginning and end of team share names, causing the inability to sync the team share
• Fixed a bug where email notifications couldn't process some international Unicode characters in file/folder names or texts properly and emails failed to send
• Fixed a rare bug where several identical emails could be sent if triggered by the same action (such as download of the same file by the same person)
• Fixed a bug where a share link owner was not notified via email when their link expired
• Fixed a bug where emails with international Unicode characters in subject and body (for example, notifications mentioning files/folders with such characters in names) were failing to send in some cases
• Fixed a bug where drag-and-drop upload within a shared folder would always bring the user back to the top level of the shared folder, no matter how deep in the folder structure the user was. Now, the user will remain in the current folder after uploading
• Fixed a bug where drag-and-drop upload into a sub-folder by hovering files over its name didn't work properly within a shared folder, uploading the file in the currently opened folder instead
• Fixed a bug where making a new guest account from the share link dialog (by adding a new email to recipients) and saving changes twice without refreshing the page would revoke access of the newly created guest account to that share link
• Fixed a bug in file listing API where sorting worked only for the first page of 20 items. Now, sorting works correctly for the whole folder in iOS and Android apps and other API integrations
• Fixed a bug in the API where deleting an organization didn't delete its accounts. Now, accounts are being deleted properly, same as if the organization was deleted from Web UI
• Fixed a bug where a team share would appear for a user on Web even though the user had only a machine subscription to that team share, but not a "Web and Mobile" subscription
• Fixed a bug where files on top level of a Backup root weren't included in the resulting archive when selecting them in bulk and choosing "Download Zip"
• Fixed a bug where trying to send a storage overview report and some other reports for organizations with unlimited quota would result in 500 error
• Fixed a bug where clicking the Home button in breadcrumbs on the user's list of backups would return 404 error
• Fixed the sorting of numbers in the names of team shares in user's and admin's lists. Instead of Share 1, Share 10, Share 2, Share 20, Share 3, Web now uses the proper order: Share 1, Share 2, Share 3, Share 10, Share 20
• Fixed a bug where admin's list of team shares displayed inconsistent tab icons when switching between tabs "Team Shares" and "Individual Shares"
• Fixed a bug where the locked icon didn't appear next to a file that the user just locked until a page refresh
• Fixed a bug where file and folder download requests didn't appear in web-access.log
• Fixed a bug where an org admin was able to edit an account of a system admin belonging to the same organization. Now, only system admins can edit accounts of other system admins

SUPPORT | 720-204-4500 | 800-352-0248

• Contact Axcient Support at https://partner.axcient.com/login or call 800-352-0248
• Have you tried our Support chat for quick questions?
• Free certification courses are available in the Axcient x360Portal under Training
• Subscribe to Axcient Status page for updates and scheduled maintenance

2067