VSCode plugin login failure

[gudzenkov]

CodeGPT plugin login does redirect tot http://localhost:54112/auth/callback?code=XXX Once logged in with Google, page shows Connection Success and redirect back to VSCode app.

Launched external handler for 'vscode://'.

However, nothing really happens, plugin still shows as logged out. The only log entry is this -

[15:15:51] Registering CodeGPT Copilot provider

Re-installing the plugin did not help. Removing plugin files from ~/.vscode/extensions/danielsanmedium.dscodegpt-3.2.1/ with clean install did not help. VSCode upgrade 1.86.2 to 1.87.0 did not help.

Another confusing thing is version - plugin version is 3.2.1, Chat shows 3.1.1, welcome banner shows 2.0.

VSCode Version: 1.87.0
Commit: 019f4d1419fbc8219a181fab7892ebccf7ee29a2
Date: 2024-02-27T23:42:51.279Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin arm64 23.3.0

[red-daut]

+1

Having the exact same issue.

[PilarHidalgo]

@gudzenkov @red-daut Hi guys!, try to update Node.js: 18.17.1 to Node.js 20.

[gudzenkov]

That is Node.js bundled with VSCode 1.87.0 My local node is already 21.6.2

[luqmanyusof]

facing the same issue. not redirect to VSC after web login

Version: 1.87.0 (user setup) Commit: 019f4d1419fbc8219a181fab7892ebccf7ee29a2 Date: 2024-02-27T23:41:44.469Z Electron: 27.3.2 ElectronBuildId: 26836302 Chromium: 118.0.5993.159 Node.js: 18.17.1 V8: 11.8.172.18-electron.0 OS: Windows_NT x64 10.0.22621

local node version 20.11

[camsique]

Having the same issue.

[matiaszanolli]

Mostly the same happening here. Ubuntu 23.10, VS Code Insiders (latest as of this post).

I get the "Connection Success" message" but when I click on "Open in VSCode Insider", Chrome silently fails to reach my running VSCode instance.

[bgeneto]

Some issue here. Can't login. Is there any alternative form of login to codeGPT vscode extension?

[Sarinoty]

Same issue too. I click on "Open in VSCode" after web login but nothing happens. I tried with Firefox and Chrome, same issue. I'm on Linux Mint.

[JeromeGsq]

Same issue here, vscode on macos. CodeGPT: v3.2.4 VSCode: 1.87.2

[Mayorc1978]

I cannot login, stuck here, but it worked a few months ago when i tested it: If I click signin it opens the browser at this local page: http://localhost:54112/login But get this:

VSCODE:

Versione: 1.88.0 (user setup)
Commit: 5c3e652f63e798a5ac2f31ffd0d863669328dc4c
Data: 2024-04-03T13:26:18.741Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
Sistema operativo: Windows_NT x64 10.0.19045

[bitdeep]

Can you guys provide a way to copy the token and paste in the extension via cmd? I'm stuck, can't login to cursor too.

[clintonruairi]

same problem here. Is this going to be fixed? if not I'll just use cursor

[davila7]

We have not been able to replicate the error, so far every time we log in, the account remains connected in the extension.

The only error that currently exists is that depending on the browser the buttons to return to VSCode do not work, this will be resolved in the next version.

You could follow this tutorial to confirm that the entire Login process is correctly working on your accounts.

https://youtu.be/yErnyqXobcI?si=p3Tr925PcvjvzR_h

If after following the tutorial the Connected icon still does not appear in CodeGPT, could you send me an email to daniel@codegpt.co with a video or images of the complete flow you are doing so we can fix the problem.

Thank you very much for your help reporting the error, we will try to solve it as soon as possible

[clintonruairi]

sure, I'll record it now

[clintonruairi]

Emailed you with the video!

[PilarHidalgo]

Can you guys provide a way to copy the token and paste in the extension via cmd? I'm stuck, can't login to cursor too.

no need the token just set the connection on the menu, please follow the tutorial https://youtu.be/yErnyqXobcI?si=p3Tr925PcvjvzR_h

[clintonruairi]

@PilarHidalgo

I followed the tutorial the first time. It didn't work. After you posted this message, I made sure to follow it again, very slowly, to ensure I was not doing anything incorrectly. Same result.

When prompted to sign in by the extension, it is still redirected to a dead page on localhost.

The codeGPT plugin still gets stuck on an infinite loading screen.

When manually clicking sign in from the extension bar, it still redirects to a dead page on localhost.

This problem has been echoed by dozens of your users. If this extension worked I would happily pay the annual subscription fee. If your 'solution' is that we should all watch your Youtube video again, and that it works for you, I guess we should all just use cursor instead.

https://cursor.sh/

Screencast from 2024-04-17 22-21-23.webm

[davila7]

@clintonruairi

Now that we can see the video, possibly the problem is that port 54112 or 54113 are being used by another service.

Could you check if by turning off the services that run through those ports you can now lift the extension?

[clintonruairi]

Nope, no process running on those ports. Ran the following commands:

 sudo lsof -i :54112
sudo lsof -i :54113
sudo fuser 54112/tcp   
sudo fuser 54113/tcp
sudo fuser -k 54113/tcp
sudo fuser -k 54112/tcp

First to see if there were any processes running on those ports - returned nothing. Then killing any processes on those ports, just to be sure. Then installed codeGPT, opened the sidebar - still stuck on infinite loading. Clicked the sign in prompt in the bottom right of vs code, redirected to 'Not found' link on localhost.

Screenshot:

Other things I have tried so far (all unsuccessful), each after uninstalling codeGPT, closing VS code, and then reinstalling codeGPT:

• disabled firewall
• disabled VPN
• cleared browser cache for codeGPT
• changed browser to firefox
• disabled adblocker
• made sure VS code up to date
• made sure codeGPT up to date
• tried on multiple other wifi networks
• tried on 2 other machines. Windows 11 and MacOs Sonoma 14.4.1
• restarted/ Reinstalled VS code

Behaviour is the same across all of the above configs. Leads me to believe this is almost certainly a problem with codeGPT itself, or conflicting behaviour with another extensions. My installed extensions:

code --list-extensions
cweijan.vscode-office
dbaeumer.vscode-eslint
ecmel.vscode-html-css
esbenp.prettier-vscode
file-icons.file-icons
github.github-vscode-theme
grapecity.gc-excelviewer
infeng.vscode-react-typescript
magicstack.magicpython
mkxml.vscode-filesize
monokai.theme-monokai-pro-vscode
ms-azuretools.vscode-docker
ms-python.debugpy
ms-python.python
ms-python.vscode-pylance
ms-vscode-remote.remote-containers
ms-vscode.remote-repositories
ms-vscode.vscode-typescript-next
pmneo.tsimporter
prisma.prisma
rust-lang.rust
rust-lang.rust-analyzer
tomoki1207.pdf
xabikos.javascriptsnippets
yoavbls.pretty-ts-errors

Got any suggestions? @davila7

[davila7]

Thank you for the information @clintonruairi

We are evaluating with the team what might be happening... we will keep you updated.

[Mayorc1978]

@clintonruairi

Now that we can see the video, possibly the problem is that port 54112 or 54113 are being used by another service.

Could you check if by turning off the services that run through those ports you can now lift the extension?

Used this PowerShell command to check if those ports were occupied by a service: Get-NetTCPConnection | where {$_.LocalPort -eq 54112 -or $_.LocalPort -eq 54113}

Returned nothing when VSCODE wasn't active. Returned values and PID were of a VSCODE process, suspecting it was CODEGPT, I uninstalled the extension. And now It doesn't detect it. Which means the problem is not dependent on some other process cause as soon I reinstalled again those ports were detected as used...by CodeGPT. But still cannot connect.

[Neoplayer]

Linux fedora 39.

code -v
1.88.1
e170252f762678dec6ca2cc69aba1570769a5d39
x64

[djacquensf9]

@bgeneto @matiaszanolli @clintonruairi Hi guys! I just test it on Ubuntu 22.04 and works! , just follow the tutorial is the same for Ubuntu https://youtu.be/yErnyqXobcI?si=p3Tr925PcvjvzR_h

Hi,

For info, it is not the right way to reproduce this issue. You need to do a remote connection, for example through an SSH connection to an GNU/Linux instance.

Thanks

[PilarHidalgo]

@bgeneto @matiaszanolli @clintonruairi Sorry guys, you are right. I haven't tried on the remote server yet, but I made a procedure on WSL here: https://medium.com/p/881b91ba193e