Sign in Again in Git Mac

Nearly authentication

To keep your account secure, y'all must authenticate before you lot tin use GitHub Desktop to admission resources on GitHub.

Before you cosign, yous must already accept an business relationship on GitHub.com.

• For more than information on creating an account on GitHub.com account, see "Signing upwards for a new GitHub account".
• For a GitHub Enterprise account, contact your GitHub Enterprise site administrator.

Authenticating an account on GitHub

1. In the menu bar, use the GitHub Desktop drop-down menu, so click Preferences.

2. In the Preferences window, select Accounts.

3. To the right of "GitHub.com," click Sign In.

4. In the "Sign in" pane, click Sign in using your browser. GitHub Desktop will open your default browser.

   Warning: Authenticating to GitHub using your username and password is non supported. We require authenticating using the browser instead.

5. To authenticate to GitHub, type your GitHub.com credentials and click Sign in.

   Alternatively, if you were already signed in to GitHub, follow the prompts to return to GitHub Desktop to terminate authenticating.

6. If you have configured two-factor hallmark (2FA) for GitHub, do i of the following:

   • If you lot prepare 2FA via SMS, retrieve your 2FA code from an SMS bulletin.
   • If you lot gear up 2FA with a TOTP awarding, generate a 2FA lawmaking.

   Then enter your 2FA code in the prompt on GitHub and click Verify.

7. After GitHub authenticates your account, follow the prompts to return to GitHub Desktop.

Authenticating an business relationship on GitHub Enterprise

Warning: Authenticating to GitHub using your username and countersign is non supported. We require authenticating using the browser instead.

1. In the card bar, use the GitHub Desktop drib-down menu, and then click Preferences.

2. In the Preferences window, select Accounts.

3. To the right of "GitHub Enterprise Server," click Sign In.

4. To add together a GitHub Enterprise account, type your credentials under "Enterprise server address," then click Continue.

5. If yous accept configured two-factor authentication for GitHub Enterprise, practise one of the following:

   • If you set up 2FA via SMS, recollect your 2FA code from an SMS message.
   • If you set 2FA with a TOTP application, generate a 2FA code.

   And so enter your 2FA lawmaking in the prompt on GitHub Desktop and click Sign In.

Authenticating an account on GitHub

1. Utilise the File carte, then click Options.

2. In the Options window, select Accounts.

3. To the right of "GitHub.com," click Sign in.

4. In the Sign in pane, click Sign in using your browser.

   Alert: Authenticating to GitHub using your username and password is non supported. We require authenticating using the browser instead.

5. To authenticate to GitHub, blazon your GitHub.com credentials and click Sign in.

   Alternatively, if yous were already signed in to GitHub, follow the prompts to return to GitHub Desktop to terminate authenticating.

6. If you lot have configured two-gene authentication (2FA) for GitHub, do i of the following:

   • If you ready 2FA via SMS, retrieve your 2FA code from an SMS message.
   • If you ready 2FA with a TOTP application, generate a 2FA code.

   And so enter your 2FA code in the prompt on GitHub and click Verify.

7. Afterwards GitHub authenticates your account, follow the prompts to return to GitHub Desktop.

Authenticating an account on GitHub Enterprise

1. Employ the File menu, then click Options.

2. In the Options window, select Accounts.

3. To the right of "GitHub Enterprise Server," click Sign In.

4. To add a GitHub Enterprise account, type your credentials nether "Enterprise server address," and then click Go on.

5. If you lot have configured ii-gene authentication for GitHub Enterprise, do one of the following:

   • If you prepare 2FA via SMS, call up your 2FA code from an SMS message.
   • If you ready 2FA with a TOTP awarding, generate a 2FA code.

   Then enter your 2FA code in the prompt on GitHub Desktop and click Sign In.

Troubleshooting authentication issues

If GitHub Desktop encounters an authentication error, you can use mistake messages to troubleshoot.

If you encounter an hallmark error, first try signing out and signing back in to your business relationship on GitHub Desktop.

For some errors, GitHub Desktop will prompt y'all with an error message. If you lot are not prompted, or to discover more information about any mistake, view the GitHub Desktop log files by using the following steps.

1. Use the Help drop-downwardly menu and click Bear witness Logs in Finder.
2. Select the log file from the date when you encountered the authentication error.

1. Employ the Assistance drop-downwardly carte du jour and click Testify Logs in Explorer.
2. Select the log file from the date when you encountered the authentication fault.

Review the troubleshooting information below for the error bulletin that y'all encounter.

Bad credentials

          Error: Bad credentials        

This error means that there is an outcome with your stored account credentials.

To troubleshoot, sign out of your account on GitHub Desktop and and then sign dorsum in.

Empty token

          info: [ui] [AppStore.withAuthenticatingUser] account found for repository: node -                          (empty token)                  

This error means that GitHub Desktop is unable to observe the admission token that it created in the system keychain.

To troubleshoot, sign out of your account on GitHub Desktop and and so sign dorsum in.

Repository not institute

          fatal: repository 'https://github.com//.git' not found  (The error was parsed as 8: The repository does not seem to exist anymore. You may not have access, or it may accept been deleted or renamed.)                              

This mistake means that you do non have permission to access the repository that you are trying to clone.

To troubleshoot, contact the person in your organization who administers permissions.

Could not read from remote repository

          git@github.com: Permission denied (publickey). fatal: Could not read from remote repository.  Please make sure you lot have the correct access rights and the repository exists.        

This error means that you lot do not have a valid SSH key set upwards.

To troubleshoot, come across "Generating a new SSH primal and adding it to the SSH agent."

Failed to clone

          fatal: clone of 'git@github.com:/' into submodule path '' failed Failed to clone 'src/github.com//'. Retry scheduled Cloning into ''... git@github.com: Permission denied (publickey). fatal: Could non read from remote repository. Please make sure yous take the correct access rights and the repository exists.                                                                                                  

This error ways that either the repository that yous are trying to clone has submodules that you exercise not have access to or yous do not have a valid SSH key gear up.

If you do not have access to the submodules, troubleshoot past contacting the person who administers permissions for the repository.

If you do non have a valid SSH key set up, come across "Generating a new SSH primal and calculation information technology to the SSH amanuensis."

Unable to read AskPass response

            error: unable to read askpass response from '/Users//GitHub Desktop.app/Contents/Resources/app/static/enquire-pass-trampoline.sh' fatal: could non read Username for 'https://github.com': terminal prompts disabled                      

This error can be caused by multiple events.

If the Control Processor registry entries are modified, GitHub Desktop will respond with an Authentication failed error. To check if these registry entries have been modified, follow these steps.

1. Open the Registry Editor (regedit.exe) and navigate to the following locations. HKEY_CURRENT_USER\Software\Microsoft\Command Processor\ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor\
2. Check to see if in that location is an Autorun value in either location.
3. If there is an Autorun value, delete it.

If your Windows username has extended Unicode characters, it may crusade an AskPass response error. To troubleshoot, create a new Windows user account and migrate your files to that business relationship. For more information, see "Create a user account in Windows" in the Microsoft documentation.

Further reading

• "Nearly hallmark to GitHub"

rainshatut1969.blogspot.com

Source: https://docs.github.com/en/desktop/installing-and-configuring-github-desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github

Share this post