Is this normal? Have tried from my PC at home, as well as from my PC in the office, and both have different providers. Neither have a proxy set in the Ubuntu WSL. Both use different DNS servers.
Here the specific error:
$ mix local.hex --force
** (Mix) httpc request failed with: {:failed_connect, [{:to_address, {'repo.hex.pm', 443}}, {:inet, [:inet], :nxdomain}]}
Could not install Hex because Mix could not download metadata at https://repo.hex.pm/installs/hex-1.x.csv.
$ HEX_MIRROR=https://cdn.jsdelivr.net/hex mix local.hex
** (Mix) httpc request failed with: {:failed_connect, [{:to_address, {'cdn.jsdelivr.net', 443}}, {:inet, [:inet], :nxdomain}]}
Could not install Hex because Mix could not download metadata at https://cdn.jsdelivr.net/hex/installs/hex-1.x.csv.
I have been setting up a new Ubuntu for Elixir tests, and this used to work in the past on both machines, but is now failing, so I am a little usure what might be the cause.
How do you navigate there? By your browser? Especially if you use one from Windows, it might be setup totally different from what the WSL actually used.
Looks like your DNS were unable to resolve the name.
I entered https://repo.hex.pm/ directly in my Windows Chrome browser, on both Windows 10 machines with a Ubuntu 18.04 WSL running on both. This gave me the âAccess deniedâ error. But the root problem is that I cannot install local.hex in mix, and I tought this error message was a symptom.
On both machines (Ubuntu 18.04 LTS on WSL Windows 10) I am not behind a proxy.
rb@RB-HOME:~$ ping repo.hex.pm
PING dualstack.f2.shared.global.fastly.net (151.101.2.2) 56(84) bytes of data.
64 bytes from 151.101.2.2: icmp_seq=1 ttl=54 time=13.0 ms
64 bytes from 151.101.2.2: icmp_seq=2 ttl=54 time=12.3 ms
You might want to look into trying out minirepo,
at least you have some control. Likewise, I get
same result you reported from firefox on archlinux.
I sent an email to support at hex - yesterday; No response.
The homepage to hex.pm is poison
to brave, google-chrome browser. Search
in text bar and browser crashes instantly.
Ok, the issue here was my anti virus solution on Windows (webroot) blocking ports in the WSL, but not telling me about this blocking. This has never happened in the past, but, I guess there is always a first time. Turned off my anti virus, and everything works fine, turned it on again, and then the error is reproducable.