If the command does not work without the hosting provider configured, continue below.if it stops working again, continue with step “Contact Support”.If the command works there, re-setup the hosting provider in the Preferences again and retry.If your repository is connected to GitHub, Bitbucket or another hosting provider, known to SmartGit, open the Preferences, select section Hosting Provider and get rid of the corresponding hosting provider there.SmartGit’s Hosting Provider configuration may interfere with the authentication. continue with step “Check Environment Differences”.if you are on Windows, continue with step “Check Git Credential Manager”.If the command works there, continue with step “Check Hosting Provider”.Open a Git shell from within SmartGit: right-click the offending repository in the Branches view and invoke Open Git-Shell and try to invoke the command from this shell. If they are definitely correct, continue with step “Check Credential Manager”.Otherwise, check whether the access URL is actually correct and your credentials are correct.If the command works there, continue with step “Check Git-Shell”.On Windows, you will usually just invoke cmd.exe from the Start-button.Įrror: Authentication failed for ‘…’ Step “Check Command”Ĭheck the Output view or the log-directory for the exact command which fails and try to invoke the command from an independently opened terminal/shell.While resolving authentication-related problems, it’s recommended to disable Detect remote changes option in the Preferences, section Background Commands to prevent background operations spoiling the log file with too many problems.Īn independently opened terminal/shell refers to a terminal/shell which has not been opened through SmartGit: Log denotes directory inside the Settings Directory containing SmartGit’s log files. Try authenticating via Sourcetree once again.This is a collection of common problems and resolutions related to authentication.On the Accounts tab, remove stored credentials.Click Sourcetree > Preferences > Accounts.Identify stored credentials to Bitbucket Cloud and remove them.On the "Options" window click the "Authentication" tab.On the toolbar click "Tools" > click "Options".Linux: See the resolution in: Why am I not prompted for password when pushing or pulling to my repositories in Bitbucket Cloud via HTTPS?Īdditional Steps if you are using Sourcetree and experiencing this issue.Mac OS X: Navigate to Keychain Access and clear stored credentials related to Bitbucket Cloud.Windows: Navigate to Credential Manager and clear stored credentials related to Bitbucket Cloud.Clear stored git credentials on your machine:.Make sure you are not the App Password label or your email address as the username. ![]() ![]()
0 Comments
Leave a Reply. |