ssh console and checking app says it's down but it's not

Questions / Help
11

Updates:

  1. libcluster was producing this warning:
    [warning] [libcluster:fly6pn] unable to connect to :"{app}@{ip}"
    Setting the RELEASE_COOKIE in secrets make this warning disappear.
    Of course this is not a solution since each release will create a new cookie.
  2. Created a fresh new app (thinking I missed some step or config) and still unable to connect to the running node.
    app/bin/my_app remote
Erlang/OTP 24 [erts-12.0.3] [source] [64-bit] [smp:1:1] [ds:1:1:10] [async-threads:1] [jit]

Could not contact remote node {app}@{ip}, reason: :nodedown. Aborting...