`sf org login web` timeout from Ubuntu WSL2
- Dominant language
- No language data
- Stars
- 571
- Forks
- 80
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 3
Description
### Summary
`sf org login web` from Ubuntu inside WSL2 results in a socket timeout.
`sf org open` launches my browser just fine.
### Steps To Reproduce
`sf org login web` from Ubuntu in WSL2
### Expected result
It should launch the Windows browser.
### Actual result
Got `Error (SOCKET_TIMEOUT): timeout`
### Additional information
- I'm aware of https://github.com/forcedotcom/cli/issues/3368. As far as I can tell `sf org login web` should not be broken.
- Authorize Org from VSCode (remote connection to WSL) doesn't work too
- My existing authorized orgs are working. I just can't add new ones.
- I think this is important as with agentic coding trending many developers will be working in sandboxed headless environments.
### System Information
```
Ubuntu 24.04 for WSL2
@salesforce/cli/2.150.6 wsl-x64 node-v24.13.1
```
Contributor guide
Research direction
Start by reproducing `sf org login web` under Ubuntu 24.04 in WSL2 and compare its browser-launch path with `sf org open`. Trace the timeout and WSL-to-Windows browser handoff; done means web login launches the Windows browser successfully without breaking existing authorized-org behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, node.js, ubuntu
- Domain
- cli, networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100