Self-hosted Runner setup fails with "Temporary failure in name resolution"
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
Summary
When configuring a new Bitbucket Self-hosted Runner, it is possible to encounter the following error under certain circumstances.
1
2
3
4
Wrapped by: reactor.retry.RetryExhaustedException: org.springframework.web.reactive.function.client.WebClientRequestException: auth.atlassian.com: Temporary failure in name resolution; nested exception is java.net.UnknownHostException: auth.atlassian.com: Temporary failure in name resolution
An error occurred whilst listening to RUNNER_UPDATED websocket events.
java.net.UnknownHostException: bitbucketci-ws-service.services.atlassian.com: Temporary failure in name resolutionEnvironment
Bitbucket Pipelines Self-hosted Runners on any environment.
Cause
This issue arises from the machine executing the Runner being unable to resolve the hostname, which prevents the container from establishing an online connection.
Solution
The error message suggests that your DNS is unable to resolve our domain name, which may be indicative of a network misconfiguration.
It is advisable to contact your network administrator and request that they investigate any potential issues with the DNS server.
Updated on April 11, 2025
Was this helpful?
Still need help?
The Atlassian Community is here for you.