Skip to main content

CI step logs don't load in real time


During the execution of a Harness CI pipeline, the logs for each step don't load in real time. Instead, the logs appear after the entire stage has completed.

Possible causes

This issue is typically related to network restrictions that prevent real time loading of CI step logs. Harness uses server-sent events (SSE) to stream the response while the step is running, and this could be impeded if a network device is blocking this specific type of traffic.


To determine what is preventing CI step logs from loading in real time, check the following.

Check for network restrictions

Contact your internal network team to determine if there are any restrictions or limitations imposed on server-sent events (SSE). Network devices, such as firewalls or proxies, can be configured to block or disrupt SSE traffic.

The exact steps you need to take to resolve network restrictions depends on the specific restrictions, traffic routing configuration, type of proxy, and so on. Collaborate with your network team to identify and address these restrictions.

For example, if you use an nginx reverse proxy to view the Harness UI through a VM, you might need to modify the location section of the nginx configuration, such as:

proxy_set_header Connection '';
proxy_http_version 1.1;
chunked_transfer_encoding off;

Test outside your corporate network.

To determine if the issue is specific to your corporate network, attempt to access an ongoing pipeline execution from a network outside of your corporate environment. This could be a personal network or a separate testing environment. Monitor the pipeline execution logs from this external network and observe if the logs load in real time without any delays. If the logs display as expected, it indicates that the cause is likely related to network restrictions within your corporate network.