I'm experiencing `TLS handshake timeout` errors when using FIPS-enabled GitLab Runner. Navigate to the relevant article on support.gitlab.com. What are the two primary causes for this issue, and what is the first recommended step to resolve it?
Navigate to 'https://support.gitlab.com/hc/en-us/categories/360000053919-Knowledge-Articles'. Locate and click on the 'TLS handshake timeout or SSL connection timeout when using FIPS-enabled GitLab Runner' link (ID 56) under the 'CI/CD Pipeline & Runner' category. Identify and list the two primary causes for the `TLS handshake timeout` or `SSL connection timeout` error. Identify and state the first recommended step for resolving this error. Synthesize the gathered information into a concise answer.
The agent successfully navigates to the 'TLS handshake timeout or SSL connection timeout when using FIPS-enabled GitLab Runner' article. The agent correctly identifies and lists the two primary causes for the error, which are 'the GitLab Runner has not been configured to use a FIPS-compliant TLS configuration' and 'the GitLab instance itself is not configured to use a FIPS-compliant TLS configuration'. The agent correctly states the first recommended step for resolution, which is 'Ensure that the GitLab Runner has been configured to use a FIPS-compliant TLS configuration by setting the `CIPHERS` variable in the GitLab Runner configuration file to `TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256:TLS_AES_128_GCM_SHA256`'.