Self-hosted Runner setup fails with "java.util.concurrent.TimeoutException: null"

Summary

When configuring a new Bitbucket Self-hosted Runner, it is possible to encounter the following error under certain circumstances.

This issue prevents the host from queueing for builds and executing them, as the status update to "Online" could not be sent back to Bitbucket.

Environment

Bitbucket Pipelines Self-hosted Runners, on any environment.

Diagnosis

You can ascertain whether you are affected by this issue by reviewing the Runner logs and verifying if the following error message is being generated:

Cause

There are several potential root causes for the issue at hand:

1. The most probable cause may be attributed to a network-related issue;

2. It could also be associated with the utilization of an outdated version of the Runners;

3. Additionally, this may relate to a current incident affecting Bitbucket Cloud. It is advisable to consult our StatusPage to verify if there is an ongoing incident:

   Bitbucket status

Solution

1. Please ensure that the Runner host is able to establish a connection with Bitbucket Cloud's IP addresses by permitting the IP addresses from the following list through your firewall: IP addresses and domains to allowlist in your corporate firewall

2. Please ensure that you update your Runners host version. This process can be accomplished by adhering to the guidelines outlined in the article below, specifically in the section titled "Updating a runner version": Troubleshooting runners

If the issue persists after following the steps above, please reach out to Atlassian support, or the Atlassian community for further assistance.