# Could not contact remote node reason: :nodedown. Aborting...

**URL:** <https://community.fly.io/t/could-not-contact-remote-node-reason-nodedown-aborting/5221>\
**Category:** Questions / Help\
**Tags:** elixir\
**Created:** [May 17, 2022, 4:39pm UTC](https://community.fly.io/t/could-not-contact-remote-node-reason-nodedown-aborting/5221 "2022-05-17T16:39:00Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![derrickreimer](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/derrickreimer/32/4008_2.png) [@derrickreimer](https://community.fly.io/u/derrickreimer)\
**Post date:** [June 13, 2022, 4:48pm UTC](https://community.fly.io/t/could-not-contact-remote-node-reason-nodedown-aborting/5221/3 "2022-06-13T16:48:07Z")

</div>

I’m experiencing this issue with my application.

```auto
➜ app git:(fly) fly ssh console
Connecting to top1.nearest.of.savvycal-staging.internal... complete
# app/bin/mighty remote
Erlang/OTP 24 [erts-12.1.5] [source] [64-bit] [smp:1:1] [ds:1:1:10] [async-threads:1] [jit]

Could not contact remote node savvycal-staging@fdaa:0:61d4:a7b:9d36:7c1f:f184:2, reason: :nodedown. Aborting...

```

In the logs:

```auto
2022-06-13T16:21:57Z app[7c1ff184] iad [info]Reaped child process with pid: 728, exit code: 0
2022-06-13T16:21:57Z app[7c1ff184] iad [info]Reaped child process with pid: 730, exit code: 0
2022-06-13T16:23:23Z app[7c1ff184] iad [info]Reaped child process with pid: 792, exit code: 0
2022-06-13T16:23:23Z app[7c1ff184] iad [info]Reaped child process with pid: 794, exit code: 0
2022-06-13T16:23:23Z app[7c1ff184] iad [info]Reaped child process with pid: 813 and signal: SIGUSR1, core dumped? false
2022-06-13T16:23:23Z app[7c1ff184] iad [info]Reaped child process with pid: 815 and signal: SIGUSR1, core dumped? false

```

My `env.sh.eex` file looks like this:

```auto
#!/bin/sh

# See https://fly.io/docs/getting-started/elixir/#naming-your-elixir-node
ip=$(grep fly-local-6pn /etc/hosts | cut -f 1)
export RELEASE_DISTRIBUTION=name
export RELEASE_NODE=$FLY_APP_NAME@$ip

```

And, I have a cookie configured in `mix.exs`:

```auto
  defp releases do
    [
      mighty: [
        include_executables_for: [:unix],
        # See https://fly.io/docs/app-guides/elixir-static-cookie/
        cookie: "65f7WN8jYgn95iS1JTxgV7pyUvO-uQi96CVEG8FgSdAo-dJEoaaePg==",
        applications: [
          # ...
        ]
      ]
    ]
  end

```

Which I’ve been able to confirm is being recognized in the release:

```nohighlight
# cat app/releases/COOKIE
65f7WN8jYgn95iS1JTxgV7pyUvO-uQi96CVEG8FgSdAo-dJEoaaePg==

```

I would appreciate any pointers! Happy to provide additional information as needed.

**EDIT** : **This is now solved!**

I was missing this part in my Dockerfile that is normally appended by `flyctl` when initially calling `fly launch`:

```auto
# Appended by flyctl
ENV ECTO_IPV6 true
ENV ERL_AFLAGS "-proto_dist inet6_tcp"

```

Adding these lines (specifically the `ERL_AFLAGS` one) solved the error described here. Thanks @Mark for the [excellent troubleshooting](https://github.com/superfly/docs/pull/176) ✨

---

_[View the full topic](https://community.fly.io/t/could-not-contact-remote-node-reason-nodedown-aborting/5221)._