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,557,130
Community Members
 
Community Events
184
Community Groups

BitBucket Server to Cloud Migration Wizard - Error

We've finally resolved all of the obvious errors that were thrown via the Migration Wizard and upon a new attempt, every repository comes up as Incomplete. We are trying to migrate from BitBucket Server to Cloud where the underlying server OS is Ubuntu 16.10 with GIT v2.25.5

The errors I am seeing are the following:

  • Git error: fatal: unable to find remote helper for 'https'
  • exited with code 128 saying: fatal: unable to find remote helper for 'https' we will Retry if possible

 

The full error is this (unique for every repository):

2023-04-07 13:26:06,304 WARN [bcma-0] c.a.b.p.b.g.c.PushStdioHandler$ExitHandler Git error: fatal: unable to find remote helper for 'https'
2023-04-07 13:26:06,304 WARN [bcma-4] c.a.b.p.b.j.RepositoryDataUploadJob Git push failed with message: '/usr/local/bin/git -c core.abbrev=40 -c credential.helper= -c credential.username=x-container-token push --porcelain --progress https://x-container-token@bitbucket.org/evlumadev/nrf.git refs/*:refs/*' exited with code 128 saying: fatal: unable to find remote helper for 'https' we will Retry if possible

 

Any ideas on how to remedy?

1 answer

1 accepted

0 votes
Answer accepted

SOLVED - Looks like the issue is indeed related to first having compiled git without having libcurl4-openssl-devOnce I installed libcurl, I re-compiled Git and things seem to be processing now

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events