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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Access denied when migrating repo


 i'm in the process of setting up Jira and migrating repos to BB.

What i did:

1. cloned a repo to a local drive

2. git remote set-url origin

3. git push --all

the last command returns:

remote: Invalid username or password
fatal: Authentication failed for ''

The user in atlassian is "admin" and it was created using google authentication.



1. why the bitbucket user is "keytophoto-admin" and not "admin"?

2. what the password should be? or where do i change the password?


1 answer

Hi Admin,

In bitbucket cloud, you have to create user manually there is no as such default username.

If you want to reset username password then please try this link: and make sure the email ID is link with username so you can get reset password link on that mail ID.

Thank you for the reply.

But i think the authentication problem is due to authentication used when the Atlassian account was created.

1. create an Atlassian account authenticating with Google.

2. create a BB repo.

3. git clone over https - results in the "Authentication failed " message.


no ssh keys is been used atm.

adding SSH keys and setting up .ssh/config solved the auth issue

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events