Self-hosted Runner setup fails with 404 from POST https://auth.atlassian.com/oauth/token
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
Error has been observed at the following site(s):
*__checkpoint ⇢ 404 from POST https://auth.atlassian.com/oauth/token [DefaultWebClient]Environment
Bitbucket Pipelines Self-hosted Runners, on any environment.
Cause
The cause of this issue arises from the use of incorrect or invalid authentication credentials, which prevents Runners from successfully connecting to Bitbucket and subsequently marking the Runner's status as "Online".
Solution
It is essential to verify that the OAuth credentials utilized in the command to initiate the Runner are identical to those provided by Bitbucket UI when adding a Runner.
In certain situations, clusters or credential managers may be set up to apply base64 encoding to secrets, which can lead to a "double encoding" issue that results in authentication errors. Therefore, it is important to ensure that the credentials are not being double encoded, as this could render them incorrect when utilized.
Was this helpful?