I have been invited to a client's private repo. When I log into my account on bitbucket.org, I can see the client's repos, and the fact that they are private (lock icon), and I can see that I am a member of their team. The client admin said that they gave me full access.
When I try to clone the repo using the clone button and https, I get the expected login popup, and I enter the same credentials as my bitbucket.org account. However, I get what essentially looks like authentication errors. I have researched the Atlassian documentation and the Community forums for solutions, but I didn't see anything that matches my situation.
UPDATE: Well, I feel a little foolish. I didn't notice that there was a second, SSH, popup. I entered my same user account password there, and things worked just fine. But still, it all seems pretty arcane and confusing to me. I *do* have an SSH setup for another personal account. Is this somehow related?
Error in git bash:
Cloning into 'clientrepo'...
Logon failed, use ctrl+c to cancel basic credential prompt.
And this error in Windows PowerShell:
git clone https://username@bitbucket.org/client/clientrepo.git
git : Cloning into 'clientrepo'...
At line:1 char:1
+ git clone https://username@bitbucket.org/client/clientrepo ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (Cloning into 'clientrepo'...:String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
Logon failed, use ctrl+c to cancel basic credential prompt.
bash: /dev/tty: No such device or address
error: failed to execute prompt script (exit code 1)
fatal: could not read Password for 'https://username@bitbucket.org': No error
Hi Paul, seems like you're sorted out now.
I'm not sure however why you were getting an SSH pop-up if you were cloning via HTTPS. I also understand from your message that it's associated to a different Bitbucket account, and not to the account you were using to clone. Is this correct?
Kind regards,
Ana
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.