Open the Registry Editor ( regedit.exe) and navigate to the following locations.To check if these registry entries have been modified, follow these steps. If the Command Processor registry entries are modified, GitHub Desktop will respond with an Authentication failed error. This error can be caused by multiple events. Unable to read AskPass response error: unable to read askpass response from '/Users//GitHub Desktop.app/Contents/Resources/app/static/ask-pass-trampoline.sh'įatal: could not read Username for '': terminal prompts disabled If you do not have a valid SSH key set up, see " 生成新的 SSH 密钥并将其添加到 ssh-agent." If you do not have access to the submodules, troubleshoot by contacting the person who administers permissions for the repository. This error means that either the repository that you are trying to clone has submodules that you do not have access to or you do not have a valid SSH key set up. Please make sure you have the correct access rights Retry scheduledĬloning into Permission denied (publickey). To troubleshoot, see " 生成新的 SSH 密钥并将其添加到 ssh-agent." Failed to clone fatal: clone of into submodule path '' failedįailed to clone 'src///'. This error means that you do not have a valid SSH key set up. Please make sure you have the correct access rights and the repository exists. Could not read from remote repository Permission denied (publickey).įatal: Could not read from remote repository. To troubleshoot, contact the person in your organization who administers permissions. This error means that you do not have permission to access the repository that you are trying to clone. You may not have access, or it may have been deleted or renamed.) (The error was parsed as 8: The repository does not seem to exist anymore. Repository not found fatal: repository '' not found To troubleshoot, sign out of your account on GitHub Desktop and then sign back in. This error means that GitHub Desktop is unable to find the access token that it created in the system keychain. Empty token info: account found for repository: node - USERNAME (empty token) This error means that there is an issue with your stored account credentials. Review the troubleshooting information below for the error message that you encounter. Select the log file from the date when you encountered the authentication error. Use the Help drop-down menu and click Show Logs in Explorer. If you are not prompted, or to find more information about any error, view the GitHub Desktop log files by using the following steps. If you encounter an authentication error, first try signing out and signing back in to your account on GitHub Desktop.įor some errors, GitHub Desktop will prompt you with an error message. If GitHub Desktop encounters an authentication error, you can use error messages to troubleshoot. To add a GitHub Enterprise account, type your credentials under "Enterprise address," then click Continue. In the "Options" window, on the Accounts pane, click the Sign In button next to "GitHub Enterprise". To authenticate to 你的 GitHub Enterprise Server 实例 account, type your account credentials and click Sign in.Īlternatively, if you were already signed in to 你的 GitHub Enterprise Server 实例 account, follow the prompts to return to GitHub Desktop to finish authenticating. To add an account on 你的 GitHub Enterprise Server 实例, in the "Sign in" modal window, type the URL for your instance under "Enterprise address," then click Continue. In the "Preferences" window, on the Accounts pane, click the Sign In button next to "GitHub Enterprise". 或者,如果您已登录 GitHub,请按照提示返回 GitHub Desktop 完成身份验证。Īfter GitHub authenticates your account, follow the prompts to return to GitHub Desktop.Īuthenticating an account on GitHub Enterprise Server In the "Preferences" window, on the Accounts pane, click the Sign In button next to "".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |