fly ssh console not working

Questions / Help
5

I’ve got the same problem. When I do fly ssh console -s

╰─$ fly ssh console -s
? Select instance:  [Use arrows to move, type to filter]
> fra (fdaa:0:6e5f:a7b:b9b7:6c48:6170:2)
  fra (fdaa:0:6e5f:a7b:b9b8:79bd:6db5:2)
  fra (fdaa:0:6e5f:a7b:b9b8:ced4:6fc0:2)
  fra (fdaa:0:6e5f:a7b:b9b7:8e6d:6beb:2)
  fra (fdaa:0:6e5f:a7b:b9b8:10ea:1c89:2)
  fra (fdaa:0:6e5f:a7b:b9b8:954b:cfc0:2)
  fra (fdaa:0:6e5f:a7b:b9b8:cf29:1077:2)

Not sure which one to pick here. The command picks the first one on its own but that doesn’t work. The other ones didn’t work either, I could connect to the last one but then I get this :point_down: when I want to connect to my app.

/app/bin # ./dert_gg_web remote
Erlang/OTP 24 [erts-12.3.2.2] [source] [64-bit] [smp:1:1] [ds:1:1:10] [async-threads:1] [jit:no-native-stack]

Could not contact remote node wild-frog-7798@ip, reason: :nodedown. Aborting...

env.sh.eex

Not sure whether it’s of any use, but this is my env.sh.eex. I just took it from a blog post by Miguel Coba.

#!/bin/sh

# Sets and enables heart (recommended only in daemon mode)
# case $RELEASE_COMMAND in
#   daemon*)
#     HEART_COMMAND="$RELEASE_ROOT/bin/$RELEASE_NAME $RELEASE_COMMAND"
#     export HEART_COMMAND
#     export ELIXIR_ERL_OPTIONS="-heart"
#     ;;
#   *)
#     ;;
# esac

# Set the release to work across nodes.
# RELEASE_DISTRIBUTION must be "sname" (local), "name" (distributed) or "none".
ip=$(grep fly-local-6pn /etc/hosts | cut -f 1)

export RELEASE_DISTRIBUTION=name
export RELEASE_NODE=$FLY_APP_NAME@ip
export ELIXIR_ERL_OPTIONS="-proto_dist inet6_tcp"