I'm encountering `TLS handshake timeout` or `SSL connection timeout` errors when using FIPS-enabled GitLab Runner. Navigate to the relevant article on support.gitlab.com. According to the article, what is the common cause 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 the common cause for the `TLS handshake timeout` or `SSL connection timeout` error as described in the 'Cause' section. Identify and state the first recommended step for resolving this error as described in the 'Resolution' section. 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 the common cause for the error as 'insufficient entropy available in the container'. The agent correctly states the first recommended step for resolution as 'Increase the entropy available to the system by installing `rng-tools` (for hardware generated entropy) or any tools that can provide software generated entropy in the host machine (not in the container). For Debian based distributions, run `sudo apt-get install rng-tools`. For RedHat flavours, run `sudo yum install rng-tools` to install the package.'