Fix a code host sign-in that didn't finish
When you connect your code host with Sign in with the host, Jaah sends you to the host's page and back to your profile. If the round trip doesn't finish, nothing is connected and a red message at the top of the Git tab says why. Most of these clear when you simply start again; a few need someone else.
Who can do this: every member, for their own Git accounts.
Read the message and try againโ
-
Select your initials at the bottom of the sidebar, then My Profile, then Git. The message shows above your list of accounts right after you come back from the host.
-
Match the message to what to do:
The message says What to do The connect attempt timed out. You took too long on the host's page. Connect again. That response did not match the attempt this browser started. You finished in a different browser or tab. Connect again in this one. That connect attempt belongs to a different signed-in user. Someone else signed in to Jaah in this browser meanwhile. Sign in as yourself and connect again. The authorization was declined at the host You, or the host, refused access. Connect again and allow it. did not return an authorization code or refused to complete the connection The host broke off. Connect again. Your Microsoft Entra tenant blocks this app until an administrator consents to it once. Azure DevOps only. Ask your Microsoft administrator to approve the app once, or paste a token (step 5). Connect is not set up. Contact your org admin or Jaah support. or set up with the wrong kind of GitHub app Signing in can't work yet. Contact Jaah support, and paste a token meanwhile (step 5). -
To connect again, select + at the top right of the list. In Type, pick your host.
-
In Method, pick Sign in with the host, for example Sign in with GitHub, select the button named for the host, and allow access on the host's page. Back on Git, a green message says the account is connected and the new row has a green tick.
-
If signing in keeps failing, pick Paste a token in Method instead. Create a token on the host with read and write access to repositories, paste it in Token (Azure DevOps also asks for the Organization), and select Test and connect.
-
Check the Git list: your account's row shows Connected.
A yellow message insteadโ
Waiting for an organization owner to approve the GitHub App. is not a failure: your account was saved, but the GitHub organization's owner still has to approve Jaah before tasks can reach its repositories. See Reach a GitHub organization's repositories.
Relatedโ
- Connect your GitHub, GitLab or other code host: every way to connect, and keeping accounts working.
- Add a second account on the same code host: more than one account on one host.
- Set up your profile: the rest of your first-week settings.