WSL环境下Elm install持续报ConnectionTimeout错误求助

Hey there! Let's work through why Elm's package manager is throwing connection timeouts in your WSL environment, even though curl and Chrome can access the package repos just fine. Here are some targeted fixes to try:

• Check WSL proxy settings
  WSL often inherits Windows proxy configurations, but sometimes the setup doesn’t play nice with Elm. First, check if proxy variables are set with:
  echo $HTTP_PROXY $HTTPS_PROXY
  If you see proxy URLs here, try temporarily unsetting them and rerunning the install command:
  unset HTTP_PROXY HTTPS_PROXY && elm install elm/random
  If you need a proxy for WSL, note that localhost in WSL doesn’t map directly to Windows’ localhost—replace it with your Windows machine’s local LAN IP (e.g., 192.168.1.100:8080) instead.

• Verify Elm’s package registry configuration
  Make sure Elm is pointing to the official package source. Open the config file at ~/.elm/0.19.1/package.json (adjust the version number if you’re using a different Elm release) and check that the registry field is set to https://package.elm-lang.org. If it’s been modified, revert it to the official URL.

• Switch to WSL 2 (if on WSL 1)
  WSL 1 has known network compatibility issues compared to WSL 2. To switch your distro:

  1. Run wsl --list --verbose to get your distro name.
  2. Run wsl --set-version <YourDistroName> 2 (this might take a few minutes).
  3. Restart WSL and try the install command again.

• Clear Elm’s local cache
  Corrupted cache files can cause unexpected connection issues. Delete the cached package data with:
  rm -rf ~/.elm/0.19.1/packages ~/.elm/0.19.1/stuff
  Then rerun elm install elm/random—this will force Elm to fetch fresh copies of the packages.

• Check firewall/security software
  Windows Firewall or WSL’s local firewall (like ufw) might be blocking Elm’s outgoing requests. For testing:

  • Temporarily disable Windows Firewall (remember to re-enable it after testing).
  • If using ufw in WSL, run sudo ufw disable and try the install again.

• Manually install the problematic package
  If all else fails, you can manually add the elm/random 1.0.0 package to Elm’s cache:

  1. Download the package tarball with:
     curl -L https://github.com/elm/random/archive/refs/tags/1.0.0.tar.gz -o random-1.0.0.tar.gz
  2. Create the target directory:
     mkdir -p ~/.elm/0.19.1/packages/elm/random/1.0.0
  3. Extract the tarball into the directory:
     tar -xzf random-1.0.0.tar.gz -C ~/.elm/0.19.1/packages/elm/random/1.0.0 --strip-components=1
  4. Now run elm-test init again—it should detect the locally cached package.

Hope one of these solutions gets your Elm setup working smoothly in WSL! If you hit any roadblocks with any of these steps, feel free to share more details.

内容的提问来源于stack exchange，提问作者White Piano