Problem

Encountered the following error while starting the traceability agent: "Error: Traceability Agent Failed. dial tcp ingestion-ip:443: i/o timeout."

One possible reason for this behavior is explained below.

Resolution

The root cause of the error could be that the CENTRAL_REGION parameter is set while an HTTP proxy is being used.

This means that CENTRAL_REGION enforces the use of the single entry point with the Lumberjack protocol, which is not suitable for an HTTP proxy.

Here’s why this setup is incorrect:

With the use of CENTRAL_REGION, the agent uses the service endpoint for the configured region and uses the single entry (SINGLE URL) to route the traffic. When using single entry the TA(traceability) defaults to lumberjack and with the use of proxy, a socks based proxy is required to route the traffic for ingesting the event. This can be done by setting TRACEABILITY_PROXYURL=sock5://proxy-host:port. The communication with this config will be TA -> SOCKS Proxy -> Single Entry -> Event Ingestion service .

If an HTTP-based proxy is in use, the TA can be set up to connect directly (via the HTTP proxy) to service endpoints without routing through a single entry point. This setup will necessitate opening ports for:

• Axway ID: host: login.axway.com, port: 443
• Central host: central.eu-fr.axway.com, port: 443
• Event Ingestion Service host: ingestion.visibility.eu-fr.axway.com, port: 443
• Platform host: platform.axway.com:443

• Using the CENTRAL_REGION setting, which defaults to a single entry point and the Lumberjack protocol for event ingestion, will require a SOCKS-based proxy.

CENTRAL_REGION: EU
CENTRAL_PROXYURL: <http://customer-proxy>:<port>
TRACEABILITY_PROXYURL: <sock5://customer-proxy>:<port>

• Without the CENTRAL_REGION parameter and without a single entry point, you can access services directly via an HTTP-based proxy. For event ingestion, use HTTPS.

CENTRAL_URL: https://central.eu-fr.axway.com
TRACEABILITY_HOST: ingestion.visibility.eu-fr.axway.com:443
TRACEABILITY_PROTOCOL: https
CENTRAL_PROXYURL: <http://customer-proxy>:<port>
TRACEABILITY_PROXYURL: <http://customer-proxy>:<port>

Note: For other regions, you can find the values for the parameters mentioned above in the following documentation: Regions URLs