Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,027
Community Members
 
Community Events
176
Community Groups

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

Edited

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.

1 answer

1 accepted

0 votes
Answer accepted

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.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS

Atlassian Community Events