topic Re: Data Gateway Direct Access Error - Dynamic port binding is not supported when binding to localhost in Connectivity & Data Prep

Data Gateway Direct Access Error - Dynamic port binding is not supported when binding to localhost

datapumaarg — Wed, 12 Nov 2025 13:56:32 GMT

Hello Comunnity,

I followed all the installation instructions from the official documentation for Qlik Data Gateway – Direct Access.
The installation process completes successfully, but when running the following command to configure the tenant:

connectoragent qsc set_config --tenant_url XXXXXXXX.us.qlikcloud.com

the service fails to start and returns the following error message:

Dynamic port binding is not supported when binding to localhost. You must either bind to 127.0.0.1:0 or [::1]:0, or both.

I have tested this using a cleam SO Windows Server 2025, 2022, and 2019, (AWS Ec2 instances) and the issue occurs in all of them.

The environment includes the following .NET runtimes, which are installed automatically with the latest Qlik Data Gateway (Direct Access) installer:

Could you please confirm if this is a known issue or if any specific .NET version or configuration is required to support Kestrel on these Windows versions?

Thank you for your help.

Best regards,

This is the full error message:

C:\Program Files\Qlik\ConnectorAgent\ConnectorAgent>connectoragent qsc set_config --tenant_url XXXXXXX.us.qlikcloud.com
connector-agent starting as standard .net core process....
{"TimeStamp":"12-11-2025 13:32:21.729","ProcessId":"3128","Thread":"1","Level":"INFO","PipeName":null,"Source":"QVX","ReloadId":"NA","TenantId":"NA","UserIdType":"NA","UserId":"NA","EngineSessionId":"NA","AppId":"NA","RequestGuid":"NA","Message":"environment-info: GatewayVersion=1.7.8, AgentVersion=1.31.2, ProcessorCount=2, WorkingSet=35 MB, OS=Microsoft Windows NT 10.0.17763.0, TimeZoneOffset=00:00 (0.0)","Exception":null}
{"TimeStamp":"12-11-2025 13:32:21.903","ProcessId":"3128","Thread":"1","Level":"INFO","PipeName":null,"Source":"QVX","ReloadId":"NA","TenantId":"NA","UserIdType":"NA","UserId":"NA","EngineSessionId":"NA","AppId":"NA","RequestGuid":"NA","Message":"Using default port from config 0","Exception":null}
{"TimeStamp":"12-11-2025 13:32:21.903","ProcessId":"3128","Thread":"1","Level":"INFO","PipeName":null,"Source":"QVX","ReloadId":"NA","TenantId":"NA","UserIdType":"NA","UserId":"NA","EngineSessionId":"NA","AppId":"NA","RequestGuid":"NA","Message":"Setting CONNECTOR_AGENT_PORT for non-default port","Exception":null}
{"TimeStamp":"12-11-2025 13:32:24.312","ProcessId":"3128","Thread":"1","Level":"INFO","PipeName":null,"Source":"QVX","ReloadId":"NA","TenantId":"NA","UserIdType":"NA","UserId":"NA","EngineSessionId":"NA","AppId":"NA","RequestGuid":"NA","Message":"Log options enabled: 'NONE'","Exception":null}
{"TimeStamp":"12-11-2025 13:32:24.317","ProcessId":"3128","Thread":"1","Level":"WARN","PipeName":null,"Source":"DAG","ReloadId":"NA","TenantId":"NA","UserIdType":"NA","UserId":"NA","EngineSessionId":"NA","AppId":"NA","RequestGuid":"NA","Message":"If AGENT_LOG_OPTIONS are configured, then at least one logging option must be enabled. All non-verbose logging options at the current AGENT_LOG_LEVEL will be enabled.","Exception":null}
{"TimeStamp":"12-11-2025 13:32:24.318","ProcessId":"3128","Thread":"1","Level":"INFO","PipeName":null,"Source":"DAG","ReloadId":"NA","TenantId":"NA","UserIdType":"NA","UserId":"NA","EngineSessionId":"NA","AppId":"NA","RequestGuid":"NA","Message":"Trace: RelayCommand enabled and will be output to DirectAccessAgent.log","Exception":null}
{"TimeStamp":"12-11-2025 13:32:24.319","ProcessId":"3128","Thread":"1","Level":"INFO","PipeName":null,"Source":"QVX","ReloadId":"NA","TenantId":"NA","UserIdType":"NA","UserId":"NA","EngineSessionId":"NA","AppId":"NA","RequestGuid":"NA","Message":"Chunks ack capability is not supported","Exception":null}
{"TimeStamp":"12-11-2025 13:32:24.71","ProcessId":"3128","Thread":"1","Level":"INFO","PipeName":null,"Source":"DAG","ReloadId":"NA","TenantId":"NA","UserIdType":"NA","UserId":"NA","EngineSessionId":"NA","AppId":"NA","RequestGuid":"NA","Message":"AsyncLoadDataRequest is disabled. Connector startup timeout set to 30 seconds per attempt with 3 max attempts","Exception":null}
{"TimeStamp":"12-11-2025 13:32:26.935","ProcessId":"3128","Thread":"1","Level":"ERROR","Message":"System.InvalidOperationException: Dynamic port binding is not supported when binding to localhost. You must either bind to 127.0.0.1:0 or [::1]:0, or both.\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.LocalhostListenOptions..ctor(Int32 port)\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.ParseAddress(String address, Boolean& https)\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.AddressesStrategy.BindAsync(AddressBindContext context, CancellationToken cancellationToken)\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(ListenOptions[] listenOptions, AddressBindContext context, Func`2 useHttps, CancellationToken cancellationToken)\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.BindAsync(CancellationToken cancellationToken)\r\n at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken)\r\n at Microsoft.AspNetCore.Hosting.WebHost.StartAsync(CancellationToken cancellationToken)\r\n at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage)\r\n at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token, String startupMessage)\r\n at Microsoft.AspNetCore.Hosting.WebHostExtensions.RunAsync(IWebHost host, CancellationToken token)\r\n at Microsoft.AspNetCore.Hosting.WebHostExtensions.Run(IWebHost host)\r\n at Qlik.ConnectorAgent.AgentProcessBase.StartAgent(String[] args, Boolean isService)","Exception":null}

Re: Data Gateway Direct Access Error - Dynamic port binding is not supported when binding to localhost

Andrea_Bertazzo — Wed, 12 Nov 2025 14:47:03 GMT

As far as we know, the error "Dynamic port binding not supported" when configuring Qlik Data Gateway Direct Access on Windows Server 2019-2025 with .NET 8.0.21 could be due to a few potential causes:

Unsupported .NET version: Qlik Data Gateway requires specific .NET versions. Make sure you have .NET 4.8, .NET 6.0.x (for versions prior to 1.6.8), and .NET 8.0.x installed. Installing versions higher than 8.0.x is not supported.
Port conflicts: The gateway uses specific internal ports (e.g. 5050, 9027, 3005, 50260) for communication. Ensure these ports are not being used by other applications.
Incorrect installation: The gateway should be installed on a dedicated Windows Server, not alongside other Qlik products or on the database server itself.
Time synchronization issues: Ensure the Windows server time is aligned with the Qlik Cloud tenant's timezone to prevent disconnections.
Firewall/network issues: Verify that outbound HTTPS (port 443) traffic to the tenant hostname is allowed.

To resolve, try:

Verifying and correcting .NET installations
Checking for port conflicts
Performing a clean reinstall of the gateway
Synchronizing server time
Confirming firewall rules

Let me know if this helps

Re: Data Gateway Direct Access Error - Dynamic port binding is not supported when binding to localhost

datapumaarg — Wed, 12 Nov 2025 15:10:04 GMT

Hi Andrea,

Thank you for your detailed response. I went through each of the points you mentioned and wanted to share my findings:

1 – .NET version
I tried installing only the .NET 6.0.x versions to ensure compatibility, but during the installation process the Qlik Data Gateway executable prompted me to install .NET 8.0.x anyway. Even after having both .NET 6.0.x and 8.0.x installed, the same “Dynamic port binding not supported when binding to localhost” error persisted.

2 – Port conflicts
There are no other services running on the Windows Server. These are completely clean OS installations (Windows Server 2019, 2022, and 2025), each deployed as a fresh EC2 instance in AWS specifically for this purpose. No other Qlik products or additional software are installed or running.

3 – Dedicated installation
As mentioned above, the installations were performed on dedicated Windows instances, not shared with any other Qlik component or database.

4 – Time synchronization
The Windows server time is synchronized and aligned with the Qlik Cloud tenant’s timezone, so no discrepancy there.

5 – Network configuration
The instance has all outbound traffic allowed through a NAT gateway (no inbound ports open except RDP). Outbound HTTPS (port 443) is fully permitted.

Based on these tests and configurations, it doesn’t seem that the issue is related to the environment setup.
I’m sharing this here in case others have come across a similar situation or have suggestions on what else to try. I’d really appreciate any additional insights or ideas.

Best regards,