-
Notifications
You must be signed in to change notification settings - Fork 302
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot connect to projects in WSL after upgrading to Windows 11 24H2 if BBR2 is enabled #10540
Comments
@Atry The log is from a second window connecting to server from another (or previous) WSL window ('..Connecting to daemon started by other WSL window...) Can you close all windows, wait a few seconds, and open a new WSL window?
Then we can see what's the problem with starting the server. Something else you should try to restart WSL
|
The log of a new Remote WSL window:
|
I can browse http://127.0.0.1:33883/version , and the content is
and
|
The WSL server startup looks fine. The server is up and running. But the client can't connect. The error comes from VS Code noy being also to resolve the remote. Can you check other logs? |
And in the WSL file system: |
Does the problem reproduce with other distros as well? E.g. Ubuntu |
Yes. The same error occurs on Ubuntu after upgrading to 24H2
…On Fri, Dec 6, 2024 at 08:46 Martin Aeschlimann ***@***.***> wrote:
Does the problem reproduce with other distros as well? E.g. Ubuntu
—
Reply to this email directly, view it on GitHub
<#10540 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAES3OSWJ6JEVBZREPXZRZT2EHIFPAVCNFSM6AAAAABTDVWSU2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRTG4YTGMRZGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
The logs to connect WSL Ubuntu
|
According to the Reddit comment, it's due to broken BBR2 support in 24H2. I switched congestion provider to CTCP and now I can use Remote WSL. |
@Atry Thanks for the information. |
Steps to Reproduce:
What is interesting is that I can connect to projects in WSL via Remote Tunnel + Remote WSL, but I cannot connect to projects in WSL via Remote WSL only
The text was updated successfully, but these errors were encountered: