vscode-pull-request-github: Unable to sign in - Error code 801

I got around this, however, by clicking the Sign in button, and then going to the bottom where it where “Signing into GitHub”, where VSCode then asks you for a token. Go to https://github.com/settings/tokens and create a new token and paste that into then screen box. Then type Github.com in the next box. You are then connected.

Same issue for me on Ubuntu 19.04, Firefox 68.0.2, vscode 1.37.1, extension version 0.10.0.

The only workaround I found was to make Chrome my default browser temporarily, so apparently the login workflow is broken in Firefox.

I faced the same issue on Win10 with Edge and found the following workaround: Restart the sing in procedure from vs code. When Edge is opened, do not continue the procedure on Edge. Instead, copy the URL that from Edge to Internet Explorer and continue the process in internet explorer. That worked for me.

Hi there. I was facing the same problem and now I’m signed in.

Steps :

1. Click Sign in to github.com
2. Edge( in my case) opens the athaurization link
3. Copy the link
4. In my case, I pasted it in Firefox Developer Edition and hint Enter
5. Success message : Authorization was successful
6. Then I was redirected to VS Code.
7. That’s all and now I’m signed in.

In VS Code -> Settings, search for Github. You will find the following option:

Github: Git Authentication

- [x] Controls whether to enable automatic GitHub authentication for git commands within VS Code.

Uncheck this box to enter the Github credentials on VS Code everytime you need (instead of using your browser).

I got that problem but I fixed it. OS: Ubuntu 18.04.3 Browser: Firefox 72.0.1 VS Code version: 1.41.1 Extension version: 0.14.0

Try this:

1. Log out from “github.com” in your default browser if you are already
2. Go to VS Code and try to sign in with the extension.
3. Press continue and then try to log in
4. Success page

But after that I got an error message inside the VS Code extension. And I get stuck there for a while. Tried it again applying same procedure (because if not, I get the error page). Uninstall, Install, Disable, Enable the extension. Same error inside VS Code. I gave up.

When I was writing this comment I wanted to share my error message from inside de code editor, so I enabled the extension (and without restarting the code editor) I applied the procedure of above, got the success page and clicked on open in the pop-up box. It then logged in. Don’t know why.

Hope it is helpful.

In my case this was due to a VPN. With it disconnected it just worked. I was authenticated already so no knew login was required after disconnecting the VPN. So the login with VPN worked but it was some action after login that failed and gave me 801.

I finally got it working.

1. Opened any vscode extension in your default browser, for example change-case
2. Click “Install” button. The browser will show an alert asking how do you want to handle vscode links. Select the Visual Studio Code app
3. You now should see the extension page open in vscode

Now your browser should be able to complete the sign-in process: repeat the failed workflow and follow any alerts that instruct your browser to open vscode after the login.

Tested with macOS Big Sur, Firefox Developer Edition 85.

I had the same issue on ubuntu with firefox. The steps I did to solve this issue was the following -> 1- you go to the bottom left and click on the sync on button. 2- you sign in with github and it will open with your default browser (in my case was chrome) 3- you’ll copy the link and open a new incognito tab (private window in firefox). 4- you’ll login and it will success!

Managed to get around the issue in my browser by just reloading the page right after it showed that 801 error.

Seems like its broken in Edge Legacy. Surely stock windows 10, vscode, and github would be a tested combination at ms… How embarrassing!

Is this going to be fixed anytime soon? Concerning that you need to workaround a forced oauth signin.

Any way to use normal git remotes like you’d do for all other remotes like GitLab through vscode or are you completely forced to oauth?

A private window in Firefox was the solution for me

@makeable Same issue with Edge Legacy. Workaround: Let default browser to open github page. Copy URL, open Chrome, paste URL there and go. That worked for me, no need to change default browser.

@Shadowblitz16 for that error, the Troubleshooting Guild will help. You likely don’t have an application on your machine that handles secrets, like gnome-keyring.

This is still an issue. The “copy link to another browser” did the trick for me.

I tried signing in on Windows and Ubuntu alternatingly (3x on each). No error. However, I’ve never seen this error before.

@TylerLeonhardt Closed this issue for the 5th time!

• opened on Jun 7, 2019 · 77 comments, after 2.5 years. Can it be true?

It’s been a week and I’ve heard nothing… gonna close this for now but please let me know if you still see it.

Hi all 👋

I made a change on the auth side that I think will fix the issue for a lot of you. Can you all give it a good and let me know if you still end up seeing this issue?

Oddly enough, I got to the error 801 page, opened developer tools, refreshed the page to see whether anything would come up in the console, and it worked. Next sign-in 801’d again, and once again worked when I refreshed the page with devtools open.

You can solve this by copying and pasting token manually into VSCode:

Error code 801 is presented before reaching the “success” screen offering the auth token.

You can solve this by copying and pasting token manually into VSCode:

Thanks @cmolina, confirming this worked for me. Same scenario, Big Sur, Firefox. This was bugging my for months!

Confirmed, no need to set other browser (other than Firefox) default. Just copy Github confirmation page’s URL to Safari and continue without error (tested with latest Firefox, Safari, VScode, macOS).

Interestingly I also got the same error in brave (a chromium based browser), but when I disabled the default ad blocker and ublock origin it worked.

From the format, my first point of investigation would be, whether the vscode: protocol was correctly registered in Firefox.