Skip to main content
The 2024 Developer Survey results are live! See the results

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

9
  • Some advice is found in here and in here. There is also the alpaca project.
    – harrymc
    Commented Jul 2, 2021 at 13:12
  • @harrymc I seem to be unable to connect to the socks5 proxy on my host for some reason. When I run sudo apt-get update it just hangs as [Connecting to 192.168.1.5 (192.168.1.5)]. Any idea why?
    – VidathD
    Commented Jul 2, 2021 at 15:17
  • Have you looked at my links?
    – harrymc
    Commented Jul 2, 2021 at 19:01
  • @harrymc Yes. Before I couldn't even get to wsl to even try to connect to the proxy on 192.168.1.5:80 (192.168.1.5 is the host machine for wsl). Now it tries to connect but hangs. I didn't try the alpaca project. I don't think it is what I am looking for. Both others suggest the same thing basically. Export the http_proxy variable to be 192.168.1.5:1080. It does what it is supposed to but it still doesn't connect to the proxy on host. Like I said in the previous comment, it hangs.
    – VidathD
    Commented Jul 3, 2021 at 13:12
  • I have set the firewall rule to allow all incoming and outgoing traffic on that port. That is actually a socks5 proxy on 192.168.1.5:1080. Does that make a difference?
    – VidathD
    Commented Jul 3, 2021 at 13:18