libcluster:fly6pn] unable to connect to...

Questions / Help
1

I am getting a tonne of these on a liveview app:
[libcluster:fly6pn] unable to connect to "myapp@ip"

I have the app deployed in multi regions. I have another app, non liveview and the configs are the same but it doesn’t seem to have this issue.

2

Hi. Can I ask how’s your topology setup? Here’s an example of an app of mine called Sorteios

Can you verify if something might be missing?

This is the tutorial I’ve used:

3 
config :libcluster,
    debug: true,
    topologies: [
      fly6pn: [
        strategy: Cluster.Strategy.DNSPoll,
        config: [
          polling_interval: 5_000,
          query: "#{app_name}.internal",
          node_basename: app_name
        ]
      ]
    ]

In application.ex I have this:

topologies = Application.get_env(:libcluster, :topologies) || []

Then I have the worker as:
{Cluster.Supervisor, [topologies, [name: MyApp.ClusterSupervisor]]},

It’s worth mentioning that I am trying to scale to multi regions (3), not within the same region.

4

I’m also unable to connect the iex console at this point.
Could not contact remote node myapp@my_ip:, reason: :nodedown. Aborting...

5

Are you able to fly ssh console to your app?

6

Yes I can.

7

I’ve escalated the issue as you mentioned it’s working on another app and not this one and your config seems to be fine.

Can you direct message me the name of the broken app?

8

Thank you. I had sent an email to support about this as well. Ticket should be there.

9

I think messaging feature is disabled on my end :thinking:

10

I’ve found your email on support and added to the ticket :slight_smile:

1 Like
11

Any updates on this issue? i seem to have a similar one:

2023-10-04T16:08:47Z app[9185e04a225978] ams [info]16:08:47.801 [warning] [libcluster:fly6pn] unable to connect to :"proba@fdaa:0:8d3b:a7b:a356:3a70:5e71:2"
2023-10-04T16:08:52Z app[3287366c11d5d8] ams [info]16:08:52.111 [warning] [libcluster:fly6pn] unable to connect to :"proba@fdaa:0:8d3b:a7b:23c2:4694:acff:2"

also seems to be related to this issue

12

Yep, changing RELEASE_NODE to "${FLY_APP_NAME}@${FLY_PRIVATE_IP}" helped