Can not copy repository (git clone) & login to Azure portal (az login) via WSL in VS Code

[Hussnain-Ahmed-Orsted]

Hello everyone,

I'm facing issues with az login and Git cloning in WSL.

I'm unable to authenticate with Azure using the az login command in WSL. After entering my credentials, the following error message is displayed, and nothing happens afterwards.

A web browser has been opened at https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize. Please continue the login in the web browser. If no web browser is available or if the web browser fails to open, use device code flow with "az login --use-device-code.
('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

I was able to ping and execute other commands in WSL, which indicates that my network connection is working properly. However, I'm unable to complete the authentication process for AZ Login or Git clone.

I have tried updating all packages (sudo apt-get upgrade) and restarting the PC, but neither solution has resolved the issue.

I would appreciate it if someone could help me investigate this issue further and provide me with a solution.

Thank you for your attention to this matter.

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

• git fails to clone repository in WSL (#3869), similarity score: 0.78
• [WSL2]Git repo isn't recognized by VS Code if in linux root folder (#4559), similarity score: 0.76

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[chanpreetdhanjal]

Hi. Can you please collect networking logs by following the instructions below?
https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!