You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Logged in to bitbucket account, but does not allow cloning to occur. Detects as an invalid URL.
Hi Caden,
May I know which protocol is affected when you attempt to execute the clone command in a terminal? Is it SSH or HTTPS (or both)? Please provide any error message you see when you attempt this and try both protocols to determine if one is working.
Cheers!
- Ben (Bitbucket Cloud Support)
HTTPS:
Command: git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks ls-remote [REDACTED]
Output:
Error: remote: Invalid credentials
fatal: Authentication failed for '[REDACTED]'
SSH:
Command: git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks ls-remote git@bitbucket.org:[REDACTED]
Output:
Error: FATAL ERROR: Network error: Software caused connection abort
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Caden,.
The most common issue customers are experiencing related to authentication is due to the deprecation of GIT username/password in favour of App Passwords on 01/03/2022:
https://community.atlassian.com/t5/Bitbucket-articles/Announcement-Bitbucket-Cloud-account-password-usage-for-Git-over/ba-p/1948231
You will need to make use of an App Password for communicating to GIT via HTTPS.
We have documentation for usage of app passwords at the following link:
https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/#Create-an-app-password
Essentially, when connecting via HTTPS you will use your App Password alongside your username seperated with a ":" character.
Therefore if you are authenticating to GIT over HTTPS to push/pull you will need to update your remote URL's to include the *AppPassword*:
git remote set-url origin https://USERNAME:APP_PASSWORD@bitbucket.org/workspaceID/reposlug.git
The same applies when performing git clone:
git clone https://USERNAME:APP_PASSWORD@bitbucket.org/workspaceID/reposlug.git
I would suggest ensuring also that all stored passwords related to authentication over GIT are cleared from your machine (ie Credential Manager for Windows, Access Keychain for Mac or /etc/shadow folder for Linux).
Hope this helps.
Cheers!
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
May I also know what software you are using? The SSH error seems to relate to a software-specific problem.
Cheers!
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.