WSL2 HTTPS Connections Timeout
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 33.7k
- Forks
- 1.8k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 116
Description
Environment
Microsoft Windows [Version 10.0.19042.685]
Release: 20.04
WSL2
Linux version 4.19.128-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Tue Jun 23 12:58:10 UTC 2020
Steps to reproduce
For example, trying to install NVM fails with a timeout error.
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash
After further debugging I found that the script just tries to clone the repo using https. I then tried to clone any repo via https and it fails with a timeout error, SSH works perfectly fine.
WSL logs:
https://gist.github.com/edarioq/0198119f6c461b4025a3344a354b8d20
Expected behavior
https connections should work and git clone should work without any timeouts.
Actual behavior
fatal: unable to access 'https://github.com/nvm-sh/nvm.git/': Operation timed out after 300038 milliseconds with 0 out of 0 bytes received
Things I've tried:
- Changing MTU
- Reinstalling (brand new Windows and Ubuntu install)
- Disabling IPv6
- Updating Git
- Updating network drivers
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the timeout with the provided curl command and an HTTPS git clone, then review the linked WSL logs. Done means HTTPS connections from WSL2 complete successfully without timeouts while SSH continues to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, linux, ubuntu
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100