It stopped working again, and this time it’s not working even in empty windows. I recorded the whole process.
Thank you for the screenshare.
What is your network bandwidth. It looks like it is very slow and therefor the login process times out. I saw that it took 7 seconds for a request and this is way too long.
Ok, thank you for providing the network status.
My last suggestion is to complete deinstall Cody and reinstall again. Try also to deactivate all other extensions before installing and if Cody works then activate each extension one by one. Maybe there is an extension which disturb Cody.
I’m trying, but so far it’s not working. How can I force it to let me log in again? It’s stuck in an infinite loading screen and doesn’t let me choose any login method either.
In this case open the command palette with CTRL + SHIFT + P and choose “Developer: Reload Window”. This reloads the IDE and should complete the syncing of Cody.
i’ve been trying a lot of things
“https://www.yyoutube.com/watch?v=ocaAhdihjeU”
(i used double ‘y’ to bypass restrictions, but copy the whole URL and exclude onde ‘y’)
One more thing. Do you use any anti virus software or maybe the Windows Defender Firewall is blocking your request? What is with other extensions, do they have internet access out from WSL?
What email are you using? Is it a @gmail.com address?
Well, I’ve been using Cody for a year or more, and as I said, this issue only started this week. So I’ve never had any firewall or Windows Defender rule blocking it — at least not one created by me or with my knowledge (and I’m not sure how I could check that).
As for other extensions, I don’t really know how to properly check if they rely on an internet connection, but one thing I noticed is that I’m also unable to log into Copilot. So that might be a clue.
About the email — are you asking if I’m using a @gmail address where, exactly? In my Sourcegraph account?
That is a really good find. Did you update windows regularly and WSL too? Might be an update issue then. Try to find WSL settings in the start menu and open the network settings there to check for those settings:
Do you know how you got to that screen? I checked Windows Update and there are no pending updates. In WSL, there’s nothing important pending either (as shown in the image). Edit: I looked it up online and found out that I don’t have a .wslconfig file in my user directory — could that be the reason why that menu screen doesn’t appear for me?
You get the WSL setting from Windows if you go into the search box in the tab bar on the bottom.
What we can try additionally is that you install Cody on Windows Host so that no WSL connections is made. If you can login on Windows but not in WSL then we know that it is a WSL issue.
Earlier I tried using the search box, but when I type WSL, it only shows icons that just open a WSL instance/terminal — nothing like that settings screen. I disabled the extensions, opened a project that’s hosted on Windows, installed Cody, and it worked right away. Just one thing I’m not sure could be affecting it — I’ve switched VSCode profiles a few times, depending on which project I opened. I’m referring to VSCode’s own “profile” feature, not my Microsoft account. What do you think I should do regarding WSL?
Edit: I closed the project hosted on Windows and reopened the one on WSL, and the login happened automatically — probably because it had already succeeded on Windows, right? But I guess I should still keep investigating, since it should work normally on WSL too, right?
Yeah, please keep investigating. It looks like an issue with WSL.
In your Windows console try WSL --update. What WSL Linux instance have you installed? I have no issues, except those with networking, with a Ubuntu instance.
I ran the command wsl --update. I have Ubuntu 24.04 installed. I’ll keep investigating.
As far as I know Ubuntu 24.04 has an elevated security model. I’m using 22.04 and therefore not sure if I should upgrade or not.
I arrived at my workplace, and I previously had the slight impression that I was having more issues with the network here than at home (though that might have been a false impression), but today it worked right away, even when accessing WSL.
Workplaces might be more restricted based on security policy in companies. This is something you need to negotiate with your IT admin.
But great to hear that you are making progress at home now.