Skip to main content Skip to complementary content

Proxy and firewall allowlist information

The following tables list the most important TCP/IP ports the Talend products use.

You need to make sure that your firewall configuration is compatible with these ports or change the default ports where needed.

Non-standard ports, meaning any port other than 443 and 80, are always bound to your local network and never connect to a remote cloud system.

Add the following websites to the allowlist on every machine that runs a Talend module.
URL Port Usage Requirement level
update.talend.com 443 For downloading feature packages and monthly updates for Talend Studio. Required if updates are retrieved directly from Talend Studio without using a proxy repository nor hosting the official repositories.
talend-update.talend.com 443 For downloading external modules, either third-party Java libraries or database drivers, to connect to sources and targets in Talend Studio. This URL is also used to download updates for Talend Studio from Talend Administration Center. Required if external modules are retrieved directly from Talend Studio without using a proxy repository or if Talend Studio updates are retrieved from Talend Administration Center.
www.talend.com 443 For testing and sending usage statistics from Talend Studio. Recommended
community.qlik.com 443 For user actions, such as clicking on Community links. Recommended
help.talend.com 443 For user actions, such as clicking on help links. Recommended
https://repo1.maven.org
8082 For the ESB Runtime Features Installer - Talend Artifact Repository access. Required
Information noteTip: If your deployment depends on other third-party software, you may need to add other URLs to your allowlist. Qlik recommends adding to the allowlist all hostnames that have dynamic IP addresses.

Port information

  • Port: a TCP/IP port or a range of ports.
  • Active: Active for a standard installation of the product (Standard Installation is defined here as Server or Client installation using Talend Installer with the default values provided in the Installer User Interface).
  • Direction: In (Inbound) and Out (Outbound) refer to the direction of requests between a port and the service or CFX route communicating with it. For example, if a service is listening for HTTP requests on port 9080, then it is an inbound port because other services are performing requests on it. However, if the service calls another service on a given port, then it is an outbound port.
  • Usage: which part of the Product component uses this port (for example 1099 is used by the JMX Monitoring component of Talend Runtime).
  • Configuration file: the file or location where the value can be changed.
  • Note: anything which is important to mention additionally.

Talend Studio ports

Port Direction Usage Configuration file
8090

Active: N

IN tESBProviderRequest (SOAP Data Server) and tRESTRequest (REST Data Service default port) REST: Preferences / Talend / ESB SOAP: tESBProviderRequest component details
80

Active: N

OUT Big Data dynamic distribution only - Apache repository port (repository.apache.org)

This requirement is necessary when you have installed the 8.0.1-R2022-11 Talend Studio Monthly update or a previous one delivered by Qlik. For more information, check with your administrator.

/

Talend Identity and Access Management ports

Port Direction Usage Configuration file
9080

Active: Y

IN Talend Identity and Access Management Server - Apache Tomcat HTTP Port /conf/server.xml
9009

Active: Y

IN Talend Identity and Access Management Server - Apache Tomcat AJP Connector Port /conf/server.xml
(none)

Active: Y

OUT Talend Identity and Access Management Server - Database

By default a MySQL database is used (not network accessible). If another database should be used the port is related to the type and configuration of this database.

/conf/iam.properties

Talend Administration Center ports

Port Direction Usage Configuration file
5601

Active: Y

OUT Talend Administration Center Kibana port Configuration Page in Talend Administration Center Web-UI
8080

Active: Y

IN

Talend Administration Center Server Apache Tomcat HTTP Port

/conf/server.xml
8009

Active: Y

IN Talend Administration Center Server Apache Tomcat AJP Connector Port /conf/server.xml
10000 - 11000

Active: N

IN Talend Administration Center Server External Talend JobServer

A free port is chosen in the allotted range on the Administrator machine, where the Job will send the statistics information during its execution. Default is 10000-11000 but it can be configured to another port range.

The range of ports is only opened when real-time statistics gathering is activated for a Job.

Add scheduler.conf.statisticsRangePorts=10000-11000 to /webapps/org.talend.administrator/WEB-INF/classes/configuration.properties
(none)

Active: Y

OUT Talend Administration Center Server Database

By default a MySQL database is used (not network accessible). If another database should be used the port is related to the type and configuration of this database.

Configuration Page in Talend Administration Center Web-UI

Talend Data Preparation ports

Port Direction Usage Configuration file
5044

Active: Y

OUT Talend Data Preparation audit server port config/audit.properties
9999

Active: Y

IN Talend Data Preparation User Interface port config/application.properties
8989

Active: Y

OUT Talend Data Preparation backend port config/application.properties
27017

Active: Y

OUT MongoDB port <MongoDB>/mongod.cfg

Talend Data Stewardship ports

Port Direction Usage Configuration file
5044

Active: Y

OUT Talend Data Stewardship audit server port conf/audit.properties
27017

Active: Y

OUT MongoDB port <MongoDB>/mongod.cfg
2181

Active: Y

OUT Apache ZooKeeper port <Kafka>/config/zookeeper.properties
9092

Active: Y

OUT Apache Kafka port <Kafka>/config/server.properties
19999

Active: Y

OUT Talend Data Stewardship gateway server port config/data-stewardship.properties
19994

Active: Y

OUT Talend Data Stewardship core server port config/data-stewardship.properties
19995

Active: Y

OUT Talend Data Stewardship schema server port config/data-stewardship.properties
19996

Active: Y

OUT Talend Data Stewardship monitoring server port config/data-stewardship.properties
19997

Active: Y

OUT Talend Data Stewardship history server port config/data-stewardship.properties
19998

Active: Y

OUT Talend Data Stewardship frontend server port config/data-stewardship.properties

Talend LogServer ports

Port Direction Usage Configuration file
5044

Active: Y

IN Talend LogServer audit server port logstash-talend.conf
8057

Active: Y

IN

Talend logging module - Audit Log4j ports

logstash-talend.conf

Talend Runtime ports

Port Direction Usage Configuration file (./etc)
8000

Active: Y

IN Talend JobServer - Command Port org.talend.remote.jobserver.server.cfg
8001

Active: Y

IN Talend JobServer - File Transfer Port org.talend.remote.jobserver.server.cfg
8888

Active: Y

IN Talend JobServer - Monitoring Port org.talend.remote.jobserver.server.cfg

Talend ESB ports

Port Direction Usage Configuration file (./etc)
8040

Active: Y

IN Standard HTTP port

See HTTP configuration for more information about the configuration scripts and the admin: command which allows you to set ports to different values.

org.ops4j.pax.web.cfg
9001

Active: Y

IN Standard HTTPS port org.ops4j.pax.web.cfg
1099

Active: Y

IN JMX - RMI Registry Port org.apache.karaf.management.cfg
44444

Active: Y

IN

JMX - RMI Registry Port

org.apache.karaf.management.cfg
8101

Active: Y

IN Apache Karaf - SSH Port org.apache.karaf.shell.cfg
61616

Active: N

IN Messaging - ActiveMQ Broker Port system.properties
2181

Active: N

IN OUT ESB Locator - Apache ZooKeeper Port Server: org.talend.esb.locator.server.cfg

Client: org.talend.esb.locator.cfg

1527

Active: N

IN ESB SAM Database - Apache Derby Port

The embedded Apache Derby DB is only supported for Development and Testing purpose in production system environments. The Container, which hosts the SAM Server, needs access to the related Database port. The port depends on the Database and Database configuration.

The port value of the embedded Derby database depends on the Talend Runtime Container configuration, as the database is shipped with the container.
8082

Active: Y

OUT ESB Runtime Features Installer - Talend Artifact Repository access org.ops4j.pax.url.mvn.cfg
(*)

Active: Y

IN OUT Components deployed to the container, such as customer Services and Routes

Any of the Data Services, Routes, and other components additionally deployed to the container might require additional ports to be accessible.

Not applicable

Talend JobServer ports

Port Direction Usage Configuration file
8000

Active: Y

IN Talend JobServer - Command Port org.talend.remote.jobserver.server.cfg
8001

Active: Y

IN Talend JobServer - File Transfer Port org.talend.remote.jobserver.server.cfg
8555

Active: Y

IN Talend JobServer - Process Messaging Port <Talend JobServerPath>/conf/TalendJobServer.properties
8888

Active: Y

IN Talend JobServer - Monitoring Port org.talend.remote.jobserver.server.cfg

Talend MDM Web UI ports

Port Direction Usage Configuration file (./etc)
8057

Active: Y

OUT Talend MDM Server audit server port conf/audit.properties
8180

Active: Y

IN OUT Talend MDM Server - Tomcat HTTP port

If this port is in conflict with another application port, you can choose between the following ports: 8080, 8280, and 8380.

<TomcatPath>/conf/server.xml

8543

Active: N

IN OUT Talend MDM Server - Tomcat HTTPS port <TomcatPath>/conf/server.xml
8105

Active: Y

IN OUT Talend MDM Server - Shutdown Port <TomcatPath>/conf/server.xml
8109

Active: N

IN OUT Talend MDM Server - Tomcat AJP Port <TomcatPath>/conf/server.xml

Talend Dictionary Service Ports

Port Direction Usage Configuration file
8187

Active: Y

IN Standard port /config/data-quality.properties
27017

Active: Y

OUT MongoDB port <MongoDB>/mongod.cfg
2181

Active: Y

OUT Apache ZooKeeper port <Kafka>/config/zookeeper.properties
9092

Active: Y

OUT Apache Kafka port <Kafka>/config/server.properties

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 – please let us know!