Mix deps.get results in :could_no_establish_ssh_tunnel

Phoenix Forum Questions / Help
1

Just working through the first example in ‘Programming Phoenix’
mix phoenix.new hello
cd hello
mix ecto.create # results in lots of Unchecked depdencies, so I ran…
mix deps.get # Which results in…

Running dependency resolution
Dependency resolution completed
connection: 1.0.3
cowboy: 1.0.4
cowlib: 1.0.2
db_connection: 1.0.0-rc.3
decimal: 1.1.2
ecto: 2.0.2
fs: 0.9.2
gettext: 0.11.0
phoenix: 1.2.0
phoenix_ecto: 3.0.0
phoenix_html: 2.6.1
phoenix_live_reload: 1.0.5
phoenix_pubsub: 1.0.0
plug: 1.1.6
poison: 2.2.0
poolboy: 1.5.1
postgrex: 0.11.2
ranch: 1.2.1

  • Getting phoenix_pubsub (Hex package)
    Checking package (https://repo.hex.pm/tarballs/phoenix_pubsub-1.0.0.tar)
    > Request failed ({:could_no_establish_ssh_tunnel, {‘HTTP/1.1’, 404, ‘No such domain’}})
    > ** (Mix) Package fetch failed and no cached copy available

Any clue as to why I get this error?

BTW, the book says to use node version 5.3.0, but on Linux the latest is 4.4.7.

2

No, sorry, I can’t help with that. I tried the link in the posted errormessage and it works for me. Perhaps try again in a couple of minutes?

Also please check if you can download that tarball via wget and browser and post errormessages if any.

Thats not true. The version in the official repositories of your distribution is 4.4.7. There are a bazillion of distributions in the wild, maybe there are some which do have more recent versions and others have even older.

But I do guess you are using Ubuntu or one of its derivates (everyone does).

How to install a recent version via external repository is explained on nodejs download via package manager instructions.

If it is not ubuntu or debian based, please scroll around the linked page to find the appropriate instructions.

If that page is missing instructions for your linux, you’ll need to install from source, which you probably had to do for erlang and elixir already in that case…

3

@sinobra maybe check your environment variables, whether you’re using a http proxy which is misconfigured

env | grep http_proxy
env | grep HTTP

Best

4

Actually I think it is not just him, but perhaps some of the paths online, I’m getting an odd issue too. I just added timex to a project and this happens:

$ mix deps.get
Registry update failed (http_error)
{:failed_connect, [{:to_address, {'repo.hex.pm', 443}}, {:inet, [:inet], :nxdomain}]}
Running dependency resolution
Dependency resolution completed
  combine: 0.9.1
  timex: 2.2.1
  tzdata: 0.5.8
* Getting timex (Hex package)
  Checking package (https://repo.hex.pm/tarballs/timex-2.2.1.tar)
Request failed ({:failed_connect, [{:to_address, {'repo.hex.pm', 443}}, {:inet, [:inet], :nxdomain}]})
  Fetch failed. Using locally cached package
* Getting combine (Hex package)
  Checking package (https://repo.hex.pm/tarballs/combine-0.9.1.tar)
Request failed ({:failed_connect, [{:to_address, {'repo.hex.pm', 443}}, {:inet, [:inet], :nxdomain}]})
  Fetch failed. Using locally cached package
* Getting tzdata (Hex package)
  Checking package (https://repo.hex.pm/tarballs/tzdata-0.5.8.tar)
Request failed ({:failed_connect, [{:to_address, {'repo.hex.pm', 443}}, {:inet, [:inet], :nxdomain}]})
  Fetch failed. Using locally cached package