Vscode-pull-request-github: Error code 810 on Authentication

Created on 20 Sep 2018  路  6Comments  路  Source: microsoft/vscode-pull-request-github

  • Extension version: 0.1.5
  • VSCode Version: 1.27.2 (user setup)
  • OS: Windows 10 1803

Steps to Reproduce:

  1. Install extension
  2. Click "Sign In" prompt after restarting VS Code
  3. Approve OAuth access on GitHub
  4. Get the below page

image

Tried with Microsoft Edge.

I do see GitHub for VSCode as an authorized OAuth app in my GitHub settings.

authentication bug important

Most helpful comment

@shana Thanks, finally got this to authorize after turning off the proxy. I think this reminder should be written on the 810 page.

All 6 comments

I'm also getting this if you need an internal repro. Alias is the same as my github account.

cc: @RMacfarlane @shana

@ryzngard I finally got this to authorize after several attempts. What finally seemed to work for me was to revoke the authorization for the GitHub for VSCode app here - https://github.com/settings/applications. Then in VSCode I went to the extensions tab and clicked "reload" on the GitHub Pull Requests extension. That popped up a new "you need to sign in" dialog and that finally succeeded. This was after manually restarting VSCode several times.

Anyhoo, thought I'd pass it along in case it happens to work for you too.

Looks like a new version got pushed that fixed it. I have 0.1.6 now and it worked

This error means that there's a mismatch between the IP that started the login process and the IP that loaded the web page. That could mean that you're running a VPN that's only handling traffic for your browser, or you have some other set up that's causing the IP to change between the two requests.

@shana Thanks, finally got this to authorize after turning off the proxy. I think this reminder should be written on the 810 page.

The only way for me to get past this on enterprise was to follow https://medium.com/@brianhague/viewing-github-pull-requests-in-vscode-with-github-enterprise-859a07e6d353 . I had tried updating the settings with the personal access token already but hadn't tried the very subtle step of closing the authentication popup and just refreshing the PRs inside VSCode which finally did the trick.

Was this page helpful?
0 / 5 - 0 ratings