Install at "pleroma mix deps.get" fails

llnu commented

2019-11-19 00:54:43 +00:00

Member

Alpine linux (4.19.80-0-vanilla) fresh install
Ipv6 only connection (with dns/nat64)

I can resolve repo.hex.pm (it has ipv6 address) and wget/curl the file.

/opt/pleroma# sudo -Hu pleroma mix deps.get
!!! RUNNING IN LOCALHOST DEV MODE! !!!
FEDERATION WON'T WORK UNTIL YOU CONFIGURE A dev.secret.exs
Could not find Hex, which is needed to build dependency :phoenix
Shall I install Hex? (if running non-interactively, use "mix local.hex --force") [Yn]
** (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.

Alpine linux (4.19.80-0-vanilla) fresh install Ipv6 only connection (with dns/nat64) I can resolve repo.hex.pm (it has ipv6 address) and wget/curl the file. /opt/pleroma# sudo -Hu pleroma mix deps.get \ !!! RUNNING IN LOCALHOST DEV MODE! !!! \ FEDERATION WON'T WORK UNTIL YOU CONFIGURE A dev.secret.exs \ Could not find Hex, which is needed to build dependency :phoenix \ Shall I install Hex? (if running non-interactively, use "mix local.hex --force") [Yn] \ `** (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.`

lambadalambda commented

2019-11-19 09:47:10 +00:00

Owner

this is an ipv6 only setup?

llnu commented

2019-11-19 09:56:49 +00:00

Author

Member

yes

lambadalambda commented

2019-11-19 10:41:56 +00:00

Owner

this might be the problem. @feld you tried something like this, right?

llnu commented

2019-11-19 12:38:13 +00:00

Author

Member

My vm can only speak ipv6, but with nat64 and fake ipv6 dns entries (dns64) I can connect to ipv4 only servers. There are a few corner cases where this setup fails:
The ipv4 address is hardcoded, or the application doesnt support ipv6 at all.

Im new to to the elixir env. Do you think this issue is solely caused my mix? If yes, I can open an issue there.

My vm can only speak ipv6, but with nat64 and fake ipv6 dns entries (dns64) I can connect to ipv4 only servers. There are a few corner cases where this setup fails: The ipv4 address is hardcoded, or the application doesnt support ipv6 at all. Im new to to the elixir env. Do you think this issue is solely caused my mix? If yes, I can open an issue there.

lambadalambda commented

2019-11-19 12:39:57 +00:00

Owner

@plataformatec have you ever encountered this?

wojtekmach commented

2019-11-19 13:01:30 +00:00

Member

This looks similar to https://github.com/hexpm/hex/issues/384 and it looks like an issue with ipv6.

Could you run this command in IEx session and paste the output?

iex> :inets.start(); :ssl.start(); :httpc.request(:get, {'https://repo.hex.pm/installs/hex-1.x.csv', []}, [], [])

If it's {:error, :nxdomain} then the problem is with how OTP handles ipv6.

This looks similar to https://github.com/hexpm/hex/issues/384 and it looks like an issue with ipv6. Could you run this command in IEx session and paste the output? ```elixir iex> :inets.start(); :ssl.start(); :httpc.request(:get, {'https://repo.hex.pm/installs/hex-1.x.csv', []}, [], []) ``` If it's `{:error, :nxdomain}` then the problem is with how OTP handles ipv6.

llnu commented

2019-11-19 21:13:29 +00:00

Author

Member

iex(1)> :inets.start(); :ssl.start(); :httpc.request(:get, {'https://repo.hex.pm/installs/hex-1.x.csv', []}, [], [])
{:error,
  {:failed_connect,
  [{:to_address, {'repo.hex.pm', 443}}, {:inet, [:inet], :enetunreach}]}}

iex(1)> :inets.start(); :ssl.start(); :httpc.request(:get, {'https://repo.hex.pm/installs/hex-1.x.csv', []}, [], []) {:error, {:failed_connect, [{:to_address, {'repo.hex.pm', 443}}, {:inet, [:inet], :enetunreach}]}}

llnu commented

2019-12-29 13:55:51 +00:00

Author

Member

Input from Nico:
It seems that the connection is tried via the inet protocol however it should be from the inet6 protocol.

Input from Nico: It seems that the connection is tried via the inet protocol however it should be from the inet6 protocol.

nicoschottelius commented

2020-01-16 07:40:05 +00:00

Member

Good morning! I was wondering if there is anything I can do to support pleroma in IPv6 only situations?

lambadalambda commented

2020-01-16 10:04:28 +00:00

Owner

Well, figuring out why this happens and fixing that would be the best way to help :) Nobody on the team is probably too interested in this use case, so this is the perfect issue for an outside contributor.

feld commented

2020-05-26 20:47:39 +00:00

Owner

It's my understanding when talking with Kaniini that Erlang/BEAM isn't IPv6-only compatible, but I don't really know the details. You do need to enable ipv6 DNS resolution, though:

http://erlang.org/doc/apps/erts/inet_cfg.html:

{inet6, Bool}.
Bool = true | false

Tells the DNS client inet_res(3) to look up IPv6 addresses. Defaults to false.

You can enable inet6 support by creating a file like erl_inetrc with the following contents:

%% -- ERLANG INET CONFIGURATION FILE --
{inet6, true}.

and then you can make Pleroma use it by referencing a vm.args file with contents similar to this:

-kernel inetrc '"/usr/local/etc/pleroma/erl_inetrc"'

And finally make Pleroma use the vm.args with something like this:

elixir --erl '-args_file /usr/local/etc/pleroma/vm.args' -S mix phx.server

Anything related to IPv6 being broken with mix deps.get in Elixir should be directed upstream. It's a bug in Elixir then.

It's my understanding when talking with Kaniini that Erlang/BEAM isn't IPv6-only compatible, but I don't really know the details. You do need to enable ipv6 DNS resolution, though: http://erlang.org/doc/apps/erts/inet_cfg.html: ``` {inet6, Bool}. Bool = true | false Tells the DNS client inet_res(3) to look up IPv6 addresses. Defaults to false. ``` You can enable inet6 support by creating a file like `erl_inetrc` with the following contents: ``` %% -- ERLANG INET CONFIGURATION FILE -- {inet6, true}. ``` and then you can make Pleroma use it by referencing a `vm.args` file with contents similar to this: ``` -kernel inetrc '"/usr/local/etc/pleroma/erl_inetrc"' ``` And finally make Pleroma use the `vm.args` with something like this: `elixir --erl '-args_file /usr/local/etc/pleroma/vm.args' -S mix phx.server` Anything related to IPv6 being broken with `mix deps.get` in Elixir should be directed upstream. It's a bug in Elixir then.

Rows
Columns

Install at "pleroma mix deps.get" fails #10