Ports overview
Qlik Sense uses ports for communication between web browsers (users) and proxies, and between services in both internal and multi-node deployments.
This section provides an overview of the ports that are used in Qlik Sense.
Ports used internally within a node
The ports in the following table are used between Qlik Sense services that run on the same node. The ports do not have to be open through any firewalls.
Service | Port | Direction | Purpose |
---|---|---|---|
QPS | 4243 | Inbound |
Qlik Sense Proxy Service (QPS) REST API listen port. If web ticketing is used for security, this port is used by the software or service that requests tickets for users. If the software or service is remote, this port needs to be open to the location from which it is called. |
QRD | 4432 | Internal |
Default listen port for the Qlik Sense Repository Database (QRD). The port is used to listen for connections from the Qlik Sense Repository Service (QRS). |
Migration Service | 4545 | Internal |
This port is used by the Migration Service for app migration purposes. The service is launched and managed by the Qlik Sense Service Dispatcher (QSD). The Migration Service only runs on the central node. |
Chart Sharing Service | 4555 | Internal |
This port is used by the Chart Sharing Service for chart sharing between Qlik Sense users. The service is launched and managed by the Qlik Sense Service Dispatcher (QSD). This port uses HTTPS for communication. |
QRS | 4570 | Internal |
Certificate password verification port, only used within multi-node sites by Qlik Sense Repository Services (QRSs) on nodes other than the central node to receive the password that unlocks a distributed certificate. The port can only be accessed from localhost and it is closed immediately after the certificate has been unlocked. The communication is always unencrypted. |
QES | 4748 | Internal | This callback port is used by the Qlik Sense Repository Service (QRS) for sending HTTP events to the Qlik Sense Engine Service (QES). |
Ports used between user web browsers and proxies
The default ports are exposed to the Qlik Sense users and need to be open through any firewalls to each Qlik Sense Proxy Service (QPS) in the site.
Service | Port | Direction | Purpose |
---|---|---|---|
QPS | 443 | Inbound | Inbound user web traffic when using HTTPS. |
QPS | 4244 | Inbound | Authentication port when using Windows authentication over HTTPS. |
QPS | 80 | Inbound | Inbound user web traffic when using HTTP (optional). |
QPS | 4248 | Inbound | Authentication port when using Windows authentication over HTTP (optional). |
Ports used between nodes and Qlik Sense services
The ports in this section are used for communication between the Qlik Sense services.
In a single node site, all ports listed in this section are used by the various services, but do not need access through firewalls.
In a multi-node site, the ports in use vary depending on the services installed and running on each node. The ports need to be open in any firewalls between the nodes, but do not have to be open to the Qlik Sense users.
Minimum ports used for communication in multi-node sites
The following ports must always be open between the nodes in a multi-node site. The ports must be open to allow for synchronization, service health, and some specific operations.
Service | Port | Direction | Purpose |
---|---|---|---|
QRS | 4241 | Bi-directional between all nodes |
Communication port within multi-node sites for Qlik Sense Repository Service (QRS)-to-QRS synchronization. This port uses HTTPS for communication. |
QRS | 4242 |
Bi-directional between the central node and all proxy nodes |
This port is used for a number of operations including new user registration. |
QRS | 4444 | Between the central node and all rim nodes |
This port has two functions:
|
Ports used between master and slave schedulers
The ports in the following table are used when a slave Qlik Sense Scheduler Service (QSS) is used.
Service | Port | Direction | Purpose |
---|---|---|---|
QSS | 5050 | Inbound (from scheduler nodes only) |
This port is used by the master QSS on the central node to issue commands to and receive replies from slave QSS nodes. |
QSS | 5151 | Inbound (from the central node only) |
A slave QSS runs on a slave scheduler node and is accessed only by the master QSS on the central node. |
Ports used between a proxy node and an engine node
The ports in the following table define the minimum needed to allow regular user traffic and load balancing between a proxy node and an engine node.
Service | Port | Direction | Purpose |
---|---|---|---|
QES | 4747 | Inbound (from proxy nodes) |
Qlik Sense Engine Service (QES) listen port. This is the main port used by the QES. The port is used via the Qlik Sense Proxy Service (QPS) for communication with the Qlik Sense clients. |
QRS | 4239 | Inbound (from proxy nodes) |
Qlik Sense Repository Service (QRS) WebSocket port. The port is used via the Qlik Sense Proxy Service (QPS) by the Qlik Sense hub to obtain apps and stream lists. |
QRS | 4242 | Inbound (from proxy nodes) |
Qlik Sense Repository Service (QRS) REST API listen port. This port is mainly accessed by local Qlik Sense services. However, the port must be open to all proxy nodes in a multi-node site to deliver images and static content. |
Data Profiling Service | 4949 | Inbound (from proxy nodes) |
This port is used by the Data Profiling Service when accessing and modifying the the application load model. The service is launched and managed by the Qlik Sense Service Dispatcher (QSD). The port is access via the Qlik Sense Proxy Service (QPS). |
Ports used between a proxy node and the printing service
The Qlik Sense Printing Service (QPR) may be installed on the same node as other services or on a separate node. The ports in the following table must be accessible between a QPS and all QPRs to which the QPS can load balance traffic.
Service | Port | Direction | Purpose |
---|---|---|---|
QPR | 4899 | Inbound (from proxy nodes) |
Qlik Sense Printing Service (QPR) port. This port is used for printed export in Qlik Sense. The port is accessed by any node that runs a QPS. |
Ports example: Multi-node site
The following is an example of the ports that are used in a multi-node site that consists of five nodes.
Learn more
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!