Receiving a 404 when requesting a repository from Bitbucket over SSH.

[N1ghteyes]

We have an internal composer server (Satis) that has been running for years without issue.

A couple of weeks ago, the builds stopped working, and we now receive the following error from composer:

---

[Composer\Downloader\TransportException (404)]
The "https://api.bitbucket.org/2.0/repositories/{username}/{reponame}?field
s=-project%2C-owner" file could not be downloaded (HTTP/1.1 404 Not Found)

---

Obviously with the user/repo redacted for the sake of this post.

The repository definitely exists - it can be checked out with Git on my main work computer, we've not touched or updated the composer server in a good long time, and we've confirmed that the SSH key on the server and bitbucket still works and we can make the connection.

So, what changed with Bitbucket? and how do we resolve this?

EDIT:: For clarity, we have tested this with a number of Bitbucket repositories - all seem to have the same issue.

[N1ghteyes · Accepted solution]

The issue appears to be caused by this change in functionality on Bitbucket Cloud.

https://community.atlassian.com/t5/Bitbucket-articles/Changes-to-Bitbucket-API-Requires-Latest-Version-of-Go/ba-p/1975819

The composer server attempts to make a connection if it gets a 403, but a 404 is an exception.

Utterly stupid change.