Portal 8.4.4000.60
CTERA Portal version 8.4.x is first released with version 8.4.4000.23 and includes a number of new features, which are described in What's New in CTERA Portal Version 8.4.x.
Upgrading the CTERA Portal
Note
When upgrading from 8.2.x, you must upgrade from version 8.2.1500.58 or later.
Portals that only have one NIC can be upgraded to this version and continue with a single NIC. Portals configured to run with dual-NICs (earlier versions of 8.4.X) can also continue to function with dual-NICs. The second NIC is used when MCP and n8n services are configured.
The CTERA Portal is upgraded as described in Upgrading a CTERA Portal.
Pre-upgrade Requirements
If SHA-1 certificates are in use, they must be replaced with SHA-2-based signatures before starting the upgrade.
You cannot upgrade the portal while running a storage node migration.
General Considerations
If you are using the Thumbnails service, after upgrading the portal, from the from 8.2.1500.58 or later, you must disable and then re-enable the service.
After the first server boot at the end of the upgrade, portal components are loaded on to the data pool. Only after these components have successfully been loaded will the user interface become available.
Storage Node Considerations
You cannot upgrade the portal while running a storage node migration.
When storage nodes are deprecated and a deprecated storage node is being used, the upgrade stops with an error message.
When storage node names are changed. The upgrade includes updating the names in the user interface.
New Features
| ID Number | Description |
|---|---|
| PIM-9662, PIM-10483, PIM-10832, PIM-10963, PIM-10967, PIM-10969, PIM-10973, PIM-10974, PIM-10975 | Improvements to Fusion Direct: * Support for Microsoft Azure Blob Storage as the storage node. * Better performance handling bulk changes. |
| PIM-9982, PIM-9983, PIM-9984, PIM-9985, PIM-9986, PIM-9987, PIM-9988, PIM-9989, PIM-9990, PIM-10149, PIM-10227, PIM-10505, PIM-10533, PIM-10534, PIM-10535, PIM-10536, PIM-10537, PIM-10538, PIM-10539, PIM-10540, PIM-10541, PIM-10542, PIM-10587, PIM-10633, PIM-10634, PIM-10757, PIM-10827, PIM-10835, PIM-10886, PIM-11087 | Improved security, including resolving CVE-2026-65927, CVE-2026-79677, CVE-2026-4800, CVE-2026-41293, CVE-2026-4800, CVE-2026-65182, CVE-2026-66422, CVE-2026-68525, CVE-2026-68569, CVE-2026-65183, CVE-2026-65905, CVE-2026-65637, CVE-2026-73180, CVE-2026-78437, CVE-2026-78383, CVE-2026-75973, CVE-2026-86350, CVE-2026-76183, CVE-2026-86248, CVE-2026-77756, CVE-2026-77791, CVE-2026-77762, CVE-2026-87022, CVE-2026-73581 |
| PIM-10123 | Improved performance when migrating a large folder. |
| PIM-10301, PIM-10352 | A new option in the Virtual Portal Settings page: Allow end users to browse groups for collaboration. When on, the default, end users can select Active Directory groups to collaborate with. |
| PIM-10309, PIM-10502 | MCP OAuth Resource Server compliance has been implemented with the MCP service, making it compatible with multiple AI MCP clients. |
| PIM-10355 | More information is displayed about the collaborators when specifying content for collaboration: |
| PIM-10649, PIM-10725, PIM-10726, PIM-10736, PIM-10751, PIM-10776, PIM-10839 | Improvements to Fusion Direct. |
| PIM-10838, PIM-10846 | The MCP service endpoint is now https://<portal-host>/mcp for the Portal URL. |
| PIM-11009 | The status of Nginx and Envoy have been added to portal-manage.sh |
Resolved Issues
| ID Number | Description |
|---|---|
| PIM-8087 | The error returned when attempting to access a bucket without the correct permissions was misleading. |
| PIM-10190, PIM-10840 | The Edge Filer Syslog service frequently failed. |
| PIM-10244 | Filenames containing a + or - symbol were not listed is search results. |
| PIM-10315 | Upgrading from portal version 8.3.3300.x failed. |
| PIM-10342 | Two different total number of files were displayed in the dashboard. |
| PIM-10381, PIM-10382, PIM-10383, PIM-10384 | S3 metadata was not stored in the portal database after performing an S3 API PUT operation with CTERA Fusion Gateway. |
| PIM-10465 | The snapshot cleaner task ran continuously back-to-back which caused high CPU usage and replication lag alerts. |
| PIM-10476 | After changing provisioning, CTERA Drive Share/Protect agents could not connect to the portal. |
| PIM-10490 | Retrieving or copying files using the S3 API and CTERA Fusion Gateway failed when the filename contained the + character or URL-encoded special characters. |
| PIM-10563 | Microsoft Azure Blob Storage storage nodes could not connect to the portal when Direct Mode was disabled and Use HTTPS was enabled. |
| PIM-10596, PIM-10604 | Accessing files using the S3 API and CTERA Fusion Gateway failed or was very slow when the load was high. |
| PIM-10597 | Local quota values lagged behind the database values, which caused the replication database to lose synchronization. |
| PIM-10609 | Moving a local folder whose name contains German umlauts in macOS NFD form into a portal cloud drive created the folder but left it unresolvable through WebDAV, causing child uploads to be skipped. |
| PIM-10619 | In CTERA Portal version 8.4.4000.53, accessing the portal from CTERA Drive Connect failed. |
| PIM-10646 | Searching using a value that contained a dot (.) failed from Windows File Explorer. |
| PIM-10783 | Using the S3 API and CTERA Fusion Gateway to load over 60,000,000 files, failed. |
| PIM-10808 | In CTERA Portal version 8.4.4000.53, when both Direct Mode and antivirus protection are configured, the portal could become unresponsive. |
| PIM-10812, PIM-10813 | After a temporary DNS failure, Active Directory authentication failed. |
| PIM-10821 | In CTERA Portal version 8.4.4000.53, attempts to reshare a folder with an external user, by selecting resend option, failed. |
| PIM-10828 | Using the S3 API and CTERA Fusion Gateway with an object key length of 1024 bytes failed and a key length greater than 1024 bytes returned an HTTP 500 error instead of a Bad Request / KeyTooLong error. |
| PIM-10847 | From CTERA Portal version 8.4.4000.51, performance was degraded when accessing the portal using the WebDAV protocol. |
| PIM-10919, PIM-11054 | /etc/hosts was rewritten with mode 640 (umask 027), which caused the hosts file to be unreadable and the primary database became full and the portal became inaccessible. |
| PIM-10964 | With Fusion Gateway, the S3 endpoint was enabled on the portal but the corresponding S3 endpoint role was not displayed in the server roles. |
| PIM-10997 | In CTERA Portal version 8.4.4000.53, when Messaging and FIPS were implemented, Kafka Connect entered a continuous restart loop. |
Portal 8.3.3000.54
CTERA Portal version 8.3.x is first released with version 8.3.3000.12 and includes a number of new features, which are described in What's New in CTERA Portal Version 8.3.3000.x.
Upgrading the CTERA Portal
Note
When upgrading from 8.2.x, you must upgrade from version 8.2.1500.58 or later.
The CTERA Portal is upgraded as described in Upgrading a CTERA Portal.
Pre-upgrade Requirements
If SHA-1 certificates are in use, they must be replaced with SHA-2-based signatures before starting the upgrade.
You cannot upgrade the portal while running a storage node migration.
General Considerations
If you are using the Thumbnails service, after upgrading the portal, from the from 8.2.1500.58 or later, you must disable and then re-enable the service.
After the first server boot at the end of the upgrade, portal components are loaded on to the data pool. Only after these components have successfully been loaded will the user interface become available.
Storage Node Considerations
You cannot upgrade the portal while running a storage node migration.
When storage nodes are deprecated and a deprecated storage node is being used, the upgrade stops with an error message.
When storage node names are changed. The upgrade includes updating the names in the user interface.
New Features
| ID Number | Description |
|---|---|
| PIM-5281, PIM-5737, PIM-5738, PIM-5783, PIM-6289, PIM-6296, PIM-6300, PIM-6377, PIM-6378, PIM-7459, PIM-7546, PIM-7547, PIM-8092, PIM-8323, PIM-9946, PIM-9947, PIM-9948, PIM-9949, PIM-9950, PIM-9951, PIM-9952, PIM-9953, PIM-9954, PIM-10130, PIM-10147, PIM-10148, PIM-10506, PIM-10509, PIM-10523, PIM-10524, PIM-10525, PIM-10526, PIM-10527, PIM-10528, PIM-10529, PIM-10530, PIM-10531, PIM-10532, PIM-10586, PIM-10612, PIM-10635, PIM-10636, PIM-10739, PIM-10740, PIM-10758, PIM-10759, PIM-10827, PIM-10892 | Improved security, including resolving CVE-2024-47561, CVE-2023-44981, CVE-2024-47561, CVE-2026-65183, CVE-2026-65182, CVE-2026-73180, CVE-2026-65927, CVE-2026-66422, CVE-2026-68525, CVE-2026-65905, CVE-2026-68569, CVE-2026-65637, CVE-2026-77791, CVE-2026-79677, CVE-2026-75973, CVE-2026-86350, CVE-2026-76183, CVE-2026-78437, CVE-2026-86248, CVE-2026-78383, CVE-2026-77756, CVE-2026-77762, CVE-2026-87022, CVE-2026-73581, CVE-2026-4800. |
| PIM-6365 | When a sync is stalled, the email notification now includes the start date. |
| PIM-10066 | Ports 1443 and 1080 are required for internal portal server communication. |
| PIM-10302, PIM-10353 | A new option in the Virtual Portal Settings page: Allow end users to browse groups for collaboration. When on, the default, end users can select Active Directory groups to collaborate with. |
| PIM-10356 | More information is displayed about the collaborators when specifying content for collaboration: |
| PIM-10470, PIM-10471 | The snapshots cleaner task has been improved. |
Resolved Issues
| ID Number | Description |
|---|---|
| PIM-6176 | The CTERA Messaging service issued errors even when the status was active and running OK. |
| PIM-6186 | Logging in using the FQDN failed. |
| PIM-6222, PIM-6224 | Deleting an offline server failed. |
| PIM-6246 | Users were not able to download stub files globally because the index became invalid. |
| PIM-6381, PIM-6383 | A storage node with object lock enabled became offline after upgrading to portal version 8.3.3000.26. |
| PIM-6382 | Searching sometimes failed. |
| PIM-6401, PIM-6449 | Changing a cloud folder owner failed. |
| PIM-6403, PIM-6411 | Email templates could not be previewed. |
| PIM-6406, PIM-6407 | File uploads failed after upgrading a portal with a storage node with a name that does not conform to the latest S3 naming conventions. |
| PIM-6464, PIM-6466 | The Thumbnail service storage display was not correct: the status was N/A and no usage was displayed. |
| PIM-6489, PIM-6490 | The Thumbnail service failed to start when more than one thumbnail server was configured |
| PIM-6492 | The Portal Version field has been removed from the global administration view for the following: * The Platform Monitoring tab in the Dashboard screen. * The Status option in the Server window. |
| PIM-6675 | Setting up a additional servers in a portal cluster sometimes failed. |
| PIM-6685 | Exceptions sometimes occurred when working with quotas. |
| PIM-6827, PIM-7756 | Portal notifications mailing queue issued multiple errors to the logs. |
| PIM-6830 | An error was displayed when setting an IP range when IP-based Access Control was enabled, under Control Panel > Global Administrators Access Control. |
| PIM-6835, PIM-7678, PIM-8375 | Suspected Ransomware Attack Detected email notifications were not being sent. |
| PIM-7229 | Single sign-on to a portal from CTERA Drive Connect sometimes failed on the first attempt. |
| PIM-7262, PIM-7263 | Backing up the CTERA Portal database to an S3 Bucket failed when the bucket was Dell ObjectScale (S3). |
| PIM-7326, PIM-8079 | After setting Require password change period for a global administrator, when the password has expired, the message is to contact the administrator instead of enabling the administrator to reset the password. |
| PIM-7332, PIM-7341 | CTERA Fusion Gateway failed when the head-object included directories. |
| PIM-7397 | The user interface in Virtual Portal Settings for the External User Authentication section displayed a meaningless error for the Default label. |
| PIM-7500 | Launching CTERA InsightAI showed an error before showing Active. |
| PIM-7705 | After setting up a client certificate for a syslog server for the Edge Filer Syslog service, the certificate could not be cleared. |
| PIM-7783 | In large-scale deployments PostgreSQL autovacuum was blocked. |
| PIM-7792 | End users were unable to download files using Drive Connect when Direct Mode was set. |
| PIM-7918 | Fusion Gateway PUT operations failed when using rclone. |
| PIM-7946 | The Everpure storage node name has been changed to Everpure Flashblade (S3). |
| PIM-7955, PIM-10377 | There were checksum errors when using Fusion Gateway. |
| PIM-8260, PIM-8377, PIM-8501, PIM-8397, PIM-8398, PIM-8402, PIM-8403, PIM-8404, PIM-8538, PIM-8667 | CTERA InsightAI improvements, including: A global administrator can monitor the status of CTERA Insight AI from the portal and receive email notifications when the connector is unhealthy and a separate dedicated proxy server can be implemented. |
| PIM-8421 | New file extensions can be added to the list or files that support global file locking. Note: The application used for a new file extension must support file locking. |
| PIM-8425 | The graph in the global administrator and team administrator dashboards shows the change in the new users but the total users is only displayed as a number and not shown in the graph itself. |
| PIM-8521 | Team project approval popups were not displayed when SSO was enabled. |
| PIM-8655 | Microsoft Active Directory groups could not be searched nor fetched when connecting using the LDAP connector. |
| PIM-8706 | If OAuth 2.0 was set on one server, it was not propagated to the other servers in the cluster. |
| PIM-9173 | When using Azure Web Application Firewall (WAF), some pages in the user interface could not be displayed. |
| PIM-9430 | Enabling or disabling a user status was not written to the audit log. |
| PIM-9487 | If a user does not have a default folder group, folders could not be created in the end user portal. |
| PIM-9714 | Concurrent getZoneFolders and getZoneDevices SDK API calls failed. |
| PIM-9736 | Sometimes, the MCP server could not be accessed. |
| PIM-9764 | SSO logins sometimes failed. |
| PIM-9797, PIM-9817 | After saving a Microsoft Azure Blob Storage storage node, the HTTPS option was disabled and could not be enabled. |
| PIM-9827, PIM-9828 | An Edge filer syslog error notification was never cleared and sent nearly every minute. |
| PIM-10005 | Running FSCK on a specific folder group, completed without doing anything but without issuing an error. |
| PIM-10010 | After removing a folder from a zone defined with selected folders, the removed folder was still synced to the edge filer. |
| PIM-10029 | The CTERA InsightAI status in the portal displayed an error after messaging servers were rebooted. |
| PIM-10104 | Users could not be added when using LDAP with Entra domain services. |
| PIM-10477, PIM-10478 | CTERA Agents took a long time to connect to the portal with repeated CTTP reconnect failures and the portal was partially responsive after adding ~200 Agent licenses and applying provisioning changes. |
| PIM-10488, PIM-10489 | When using Fusion Gateway, getting or copying objects with '+' or encoded special characters failed. |
| PIM-10572, PIM-10610 | Moving a folder using CTERA Drive Connect that contains an umlaut to a portal cloud folder skipped uploading child content, which was nevertheless deleted locally. |
| PIM-10812 | The portal lost Active Directory logins after a DNS outage, requiring manual refreshing of the ACtive Directory connection in the user interface. |
| PIM-10728, PIM-10782 | Using the S3 API and CTERA Fusion Gateway to load over 60,000,000 files, failed. |
| PIM-10824, PIM-10826 | Using the S3 API and CTERA Fusion Gateway with an object key length of 1024 bytes failed and a key length greater than 1024 bytes returned an HTTP 500 error instead of a Bad Request/KeyTooLong error. |
| PIM-10965, PIM-10966 | With Fusion Gateway, the S3 endpoint was enabled on the portal but the corresponding S3 endpoint role was not displayed in the server roles. |
Known Issues
| ID Number | Description |
|---|---|
| – | Changing the IP address after installing a portal server but prior to the full deployment of portal services like Nomad and Consul, causes the deployment to fail. Workaround: Wait until all the portal services have been loaded before changing the IP address. If you changed the IP address after the installation but before the full deployment of portal services, run portal-manage.sh resetdbYou must run portal-manage.sh resetdb before initializing the portal or joining it to an existing portal cluster. |
| SP-16614 | Support users with the relevant permissions cannot create user groups, add or remove users in an existing group nor delete users. |
| SP-17928 | After changing a plan name and applying it, the process shows that zero users were updated. |
| SP-27973 | Consul and Nomad do not update after removing a server. Manually refresh the environment. |
Edge Filer 7.13.6000.27
Resolved Issues
| ID Number | Description |
|---|---|
| APP-31152 | Improved security, including resolving CVE-2026-105481, CVE-2026-105482, CVE-2026-106069, CVE-2026-106072, CVE-2026-106073, CVE-2026-106074, and CVE-2026-111497. |
Edge Filer 7.13.6000.26
Resolved Issues
Resolved the PHP2Shell Remote Code Execution (RCE) Security Vulnerabilities CVE-2026-109618 and CVE-2026-109619.
Edge Filer 7.13.6000.25
New Features
| ID Number | Description |
|---|---|
| APP-29827, APP-30849, APP-30886 | The support report content has been expanded to help with troubleshooting. |
| APP-30599,APP-30658 | Performance improvements, especially when there are many empty cloud folders and cloud folders without exceptions. |
| APP-30723, APP-30727, APP-30875, APP-30879, APP-30881, APP-30885, APP-30903, APP-30907, APP-30908, APP-30987, APP-30989, APP-30990, APP-30998 | Improvements to searches: * Monitoring the CTERA Search service has been added to the Services page. This service is enabled when the Advanced Search option has been installed on the CTERA Portal. * The search results page size has been increased to 200. * Search results require TLS validation. * A maximum number of returned results can be set. For details contact CTERA Support.  |
| APP-30804, APP-30805 | Improved security, including resolving CVE-2026-64600. |
| APP-30829, APP-30830, APP-30836, APP-30839 | macOS Spotlight improvements including changing the default number of worker processes to 5 and making this value configurable by running CLI. For details, contact CTERA Support. |
Resolved Issues
| ID Number | Description |
|---|---|
| APP-29474 | Audit logs could be set up to write to a share that pointed to an archive folder. |
| APP-30184 | POSIX ACLs were not enforced on shares on a second volume. |
| APP-30806, APP-30838 | There was a high RAM usage during a migration. |
| APP-30816 | In CTERA Edge Filer version 7.13.6000.19, if a folder was deleted while a nested file was open, the nested file is not deleted. |
| APP-30828 | A user could be added to both the blocked users group and the excluded users group. |
| APP-30831 | From CTERA Edge Filer version 7.13.6000.16, rebooting the edge filer intermittently prevented full deduplication of files. |
| APP-30832 | macOS Finder could produce different search queries based on whether Enter was pressed or not after typing the search term. |
| APP-30874 | Audited SMB traffic consumed writable tmpfs (temporary file system). |
| APP-30899, APP-30900, APP-30902 | Improvements when a Fusion Direct cloud folder is configured: * When Azure storage is used. * Uploading small files from the edge filer to the portal. |
| APP-30935, APP-30975, APP-30976 | When NAS was down, users and groups crashed. |
| APP-30988 | Directory names ending with a space or period displayed in macOS as empty. |
Edge Filer 7.12.5400.29
Resolved Issues
| ID Number | Description |
|---|---|
| APP-31165 | Improved security, including resolving CVE-2026-105481, CVE-2026-105482, CVE-2026-106069, CVE-2026-106072, CVE-2026-106073, CVE-2026-106074, and CVE-2026-111497. |
Edge Filer 7.12.5400.28
Resolved Issues
Resolved the PHP2Shell Remote Code Execution (RCE) Security Vulnerabilities CVE-2026-109618 and CVE-2026-109619.
Edge Filer 7.11.5100.39
Resolved Issues
Resolved the PHP2Shell Remote Code Execution (RCE) Security Vulnerabilities CVE-2026-109618 and CVE-2026-109619.
Cache Assist Version 3.4.3
CTERA Cache Assist version 3.4.3 runs on macOS versions 15 (Sequoia), 26 (Tahoe), and 27 (Golden Gate).
This version has been signed with CTERA's Apple Developer ID and notarized by Apple.
New Features
- CTERA Cache Assist is a Universal app: It contains native code for both Apple Silicon (M-series chips like M1, M2, M3, and M4) and Intel-based processors in a single package. macOS automatically detects which type of processor your Mac has and runs the correct codenatively at full speed on both platforms.
- From this version, updates are installed automatically and after an update, CTERA Cache Assist restarts automatically.
Fixed Issues
- Checking for an update when there is no network connectivity used to hang.
- Clicking the Help link did not open the CTERA Knowledge Base.
Upgrading From Version 3.0 or Version 3.1
You must uninstall your current CTERA Cache Assist version and remove it from the Mac PC before installing the latest version.
Note
Ignore any software update message for versions before version 3.2.
- Open CTERA Cache Assist, untick Enable, and quit the app.
- In Finder > Applications, move CTERA Cache Assist to the Trash.
- Empty the Trash. You might be prompted for an administrator password.
- Restart the Mac.
- Install the new Cache Assist version, as described below.
Installing CTERA Cache Assist
To install CTERA Cache Assist:
- Download the package from here.
- Open the downloaded file and follow the installation instructions.
- Open CTERA Cache Assist from Finder > Applications and tick Enable.
- Make sure the Finder extension is allowed:
- macOS 15 and 26: System Settings > General > Login Items & Extensions > Extensions.
- macOS 27: System Settings > General > Login Items > Extensions.
Drive Connect 5.3.2
Windows
New Features
*.localhost hostnamenow resolves to127.0.0.1 / ::1without extra configuration.- Microsoft PowerPoint files open faster.
- Windows no longer goes to sleep while a file transfer is running, so transfers aren’t interrupted.
Resolved Issues
- The client prompted you to pick a certificate when accepted issuers were not listed by the WebDAV server.
- Read-only files could not be pinned and kept on the local disk.
- Moving a file from a subfolder to the root cloud folder now syncs right away.
- Opening Microsoft Word files took a long time.
- Partial reads from Microsoft PowerPoint caused performance problems.
Known Issues
- In some cases, when Drive Connect is connected to a CTERA Portal version 8.2.1500.8.6 or earlier, SSO might not prompt the client mount. If this happens, enter the following URL in the browser:
https://portal_address/ServicesPortal/activate?scheme=x-cteradriveconnect-action:websso
macOS
New Features
*.localhost hostnamenow resolves to127.0.0.1 / ::1without extra configuration.- Microsoft PowerPoint files open faster.
- Videos stored as placeholder files now play smoothly in QuickTime Player.
Resolved Issues
- The client prompted you to pick a certificate when accepted issuers were not listed by the WebDAV server.
- Read-only files could not be pinned and kept on the local disk.
- Moving a file from a subfolder to the root cloud folder now syncs right away.
- Opening Microsoft Word files took a long time.
- Partial reads from Microsoft PowerPoint caused performance problems.
- Improved handling of Microsoft PowerPoint:
- Opening Microsoft PowerPoint files stalled the machine or increased CPU usage.
- In Integrated mode, there was an issue opening online PowerPoint files.
- Windows was significantly faster opening Microsoft PowerPoint files
Known Issues
- In some cases, when Drive Connect is connected to a CTERA Portal version 8.2.1500.8.6 or earlier, SSO might not prompt the client mount. If this happens, enter the following URL in the browser:
https://portal_address/ServicesPortal/activate?scheme=x-cteradriveconnect-action:websso