Home > Data integration > Data gateways > Upgrade gateways
Upgrade gateways
Last updated: 11/3/2026Cadence: Quarterly
Subscription model: All
Roles: Tenant Admin (TA), Data Admin (DA—for Data Movement gateways)
Last verified: 2026-09
| Initial | Recurring | |
|---|---|---|
| Estimated time | 2 hr per gateway | 30 min per gateway |
Benefits:
- Keeps gateways within Qlik's supported version window (avoids deactivation)
- Picks up bug fixes, connector updates, and security patches
- Reduces accumulated technical debt across the gateway estate
Goal
Qlik strongly recommends running the latest version of each gateway. Direct Access has a built-in version history and upgrade procedure; Data Movement gateway is upgraded via RPM. Never delete a gateway from the admin console as part of an upgrade—that would break existing data connections, since you'd be registering a new
gateway rather than re-registering the existing one.
Current Direct Access version status (see the Qlik release notes and deprecation notices for confirmed dates):
- 1.4 / 1.5—End of Life on January 31, 2026, no longer supported. Upgrade urgently.
- 1.6—End of support since June 14, 2025. End of Life confirmed for September 30, 2026—upgrade before then. Upgrade to a current 1.7.x or 1.8.x release.
- 1.7.x—Supported, but no longer the latest. Notable point releases: 1.7.16 (Jul 2026—chunks-recovery-per-connection toggle, Canada region support, File Connector custom file-extension support) and 1.7.17 (Aug 2026—benchmark test results surfaced in Administration, configurable log-retention limit, fix for
DirectAccess-1103concurrent-WebSocket-send errors). - 1.8.0—Current, released Sept 17, 2026. Adds containerized (Docker) deployment on Linux or Windows alongside the existing Windows install, automatic gateway registration from the command line, GA AWS PrivateLink support, a configurable File connector download-acknowledgment timeout, and updated OpenSSL / libcurl libraries. Upgrade from any 1.4 / 1.5 / 1.6 / 1.7.x to current is Qlik-tested but always back up first.
Tasks
| Task | TA | AA | DA | AuA |
|---|---|---|---|---|
Plan and apply Direct Access gateway upgrades (back up C:\ProgramData\Qlik\Gateway\configuration.properties first; the installer also creates a _BK copy automatically—and see the never delete the gateway from the console warning in Check gateway health) |
✓ | |||
| Plan and apply Data Movement gateway upgrades | ✓ | ✓ | ||
| Confirm gateway hosts are on a Qlik-certified OS (see gotchas: certified OS list) | ✓ | ✓ | ||
| If hosts are on .NET 8.0.21+, test the upgrade in a non-prod gateway first and apply the dynamic-port-binding fix (see gotchas: .NET 8.0.21 breaks dynamic-port binding) | ✓ | ✓ | ||
| When upgrading to 1.8.0+, decide per host whether to stay on the native Windows install or move to the new containerized (Docker) deployment—evaluate EC2-hosted gateways for AWS PrivateLink eligibility at the same time | ✓ |
Read before acting—gotchas
- .NET 6.0.x is no longer required from Direct Access v1.6.8. The gateway runtime is .NET 8.x, installed automatically during upgrade. (.NET Framework 4.8 is still needed for the installer.) .NET 8.0.21 (October 2025, carrying the CVE-2025-55315 Kestrel hardening) and later 8.0.x patches break dynamic-port binding when the gateway uses
localhost:0—bind explicitly to127.0.0.1:0/[::1]:0, or pin the host to .NET 8.0.20 until Qlik ships a gateway build that uses the new binding form. - Data Movement gateway certified OS list: RHEL 8.x / 9.x and Amazon Linux 2023. RHEL-compatible rebuilds (Rocky, AlmaLinux, Oracle Linux) fall under
corresponding and compatible Linux distributions
—usable, but Qlik Support may ask you to reproduce issues on certified RHEL. FIPS-mode Linux hosts are unsupported. CentOS 7 is past Qlik's certified baseline. Direct Access gateway is Windows-only. - Direct Access
configuration.propertiesbackup. The installer creates a_BKcopy automatically atC:\ProgramData\Qlik\Gateway\configuration.properties_BK; back up the original separately as well. Do not save backups toC:\Program Files\Qlik—its contents may be cleaned during the upgrade. If the upgrade fails, stop the Direct Access service, restore the backed-up file, and start the service again. (Containerized 1.8.0+ deployments use a different, volume-mounted config path—confirm the backup procedure for that deployment mode before relying on the Windows-path instructions above.) - 1.8.0 is additive, not a forced migration. The native Windows install remains fully supported; containerized (Docker) deployment on Linux or Windows is a new option, not a replacement. Likewise, console-based gateway registration still works—command-line registration is an additional path aimed at scripted / multi-tenant rollouts.
- AWS PrivateLink requires Qlik-side enablement first. It's GA from 1.8.0, but Qlik must confirm PrivateLink availability for your tenant and region and provide the regional service name before you create the interface VPC endpoint on your side. The gateway must be installed on an EC2 instance, and PrivateLink is not supported on Qlik Cloud Government or Qlik Cloud Government - DoD. See Review allowlists and web integrations for the allowlist implications.
References
- Upgrading and uninstalling Qlik Data Gateway - Direct Access
- Upgrading and uninstalling Data Movement gateway
- Direct Access gateway versions 1.4 and 1.5 reaching End of Life by January 31st 2026
- Direct Access gateway version 1.6.x reaching End of Life on September 30, 2026
- Configuring AWS PrivateLink for Qlik Data Gateway - Direct Access—GA setup guide, supported from gateway v1.8.0
Tags: #quarterly #data_integration #data_gateways #direct_access #data_movement #upgrade