Could not find a good candidate within 1 attempts at load balancing. [PC01] instance refused connection

12

There have been false positives with similar messages reported in the forum in the past:

https://community.fly.io/t/litefs-warning-the-app-is-not-listening-on-the-expected-address-and-will-not-be-reachable/21311

The API anomalies might not be related (although possibly I’m misunderstanding what you’re referring to there).

If the app that you’re getting these errors in doesn’t use volumes, then I would try destroying the two Machines that have been mentioned in the logs so far (d8d9790b279548 and 2866994fe413e8)—and then recreating them.

More broadly, see if there’s some correlation with Machines, regions, and the like…

You can use the client-side Fly-Prefer-Region and Fly-Force-Instance-Id headers to steer requests to particular locales.

$ curl -i -H 'Fly-Prefer-Region: otp' -H 'flyio-debug: doit' 'https://debug.fly.dev/'
1 Like