Hey Sergey,
You will need to update your remote URL - there is no workspaceID in existence named "workspace_test_ue", I would suggest logging into the Bitbucket Cloud UI and confirming the name of your workspace so you can create a repository under the right workspaceID.
If you are using HTTPS, I would suggest referring to our Sourcetree article as basic username/password was deprecated:
https://bitbucket.org/blog/deprecating-atlassian-account-password-for-git-and-bitbucket-api-activity
We have a blog post however which explains the steps to troubleshoot this issue, please follow these accordingly and this should resolve the issue:
https://community.atlassian.com/t5/Sourcetree-articles/Bug-Fix-Sourcetree-for-Windows-authentication-error-when/ba-p/1965968
As for the format for URL when authenticating over HTTPS, you will need to make use of an AppPassword 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 AppPassword alongside your username separated 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 App Password:
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.