Error=Unable to validate account; status=401: Unauthorized

gitkraken / vscode-gitlens

Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more

http://gitkraken.com/gitlens

Other

8.94k stars 1.28k forks source link

Error=Unable to validate account; status=401: Unauthorized #1911

Closed nyxb closed 2 years ago

nyxb commented 2 years ago

Unable to sign in to your GitLens+ account. Please try again. If this issue persists, please contact support. Account=VidarDev

I have trial but it dont work and on public repoistorys too

eamodio commented 2 years ago

@VidarDev Can you provide more details in the steps that lead up to this? I'm putting in some changes to make handling this a little smoother, but I'm still unsure how this happens.

Any details you can provide would be very helpful. Thanks!

winstonhenke commented 2 years ago

Also having this issue. macOS Monterey: 12.3 VS Code: Version: 1.65.2 - Commit: c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1

When version 12 first came out I was able to signup for GitLens+ and authenticate the extension in VS Code, but every time I try to update the extension past v12.0.1 I'm not able to sign in to GitLens+ and I see this error message and the following log snippet

[2022-03-20 16:29:38.554] ClientRequest.<anonymous>
FetchError: request to https://api.gitkraken.com/gitlens/checkin failed, reason: connect EADDRNOTAVAIL 127.0.0.1 - Local (0.0.0.0:50008)
[2022-03-20 16:29:38.554] Object.checkInAndValidateCore
Error: Unable to validate account; status=undefined: undefined

If I downgrade the extension and install v12.0.1 again then it works. I actually don't even need to sign in again then, it recognizes that I already have.

github-actions[bot] commented 2 years ago

This issue needs more information and has not had recent activity. Please provide the missing information or it will be closed in 7 days. Thanks!

winstonhenke commented 2 years ago

Also tried

Logging out of the extension
Uninstalling the extension
Re installing the latest version
Still no dice. Reverting it back to v12.0.1 fixed it for me again

eamodio commented 2 years ago

@winstonhenke From that error (and that things work in 12.0.1 which didn't have proxy support) it seems that GitLens is trying to use a configured proxy server. Do you have a proxy server configured in VS Code or in your shell environment?

GitLens honors the VS Code http.proxySupport support setting which you set to 'off' to disable any proxy support. Or if you want to do it explicitly for GitLens you can set "gitlens.proxy": { "url": null }.

If you try setting one of those does it resolve the issue?

winstonhenke commented 2 years ago

@eamodio well holy moly that worked. I have no idea why I ever changed http.proxySupport in the first place but that was my issue. Thanks.

github-actions[bot] commented 2 years ago

This issue needs more information and has not had recent activity. Please provide the missing information or it will be closed in 7 days. Thanks!

github-actions[bot] commented 2 years ago

Closing this issue because it needs more information and has not had recent activity. Please re-open this issue if more details can be provided. Thanks!

github-actions[bot] commented 2 years ago

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.