Getting errors with flyctl

1

For version update:

$ flyctl version update

WARN failed querying for new release: Get "https://api.fly.io/app/flyctl_releases/darwin/arm64/latest": dial tcp: lookup api.fly.io on 192.168.2.254:53: no such host

Error failed determining latest release: Get "https://api.fly.io/app/flyctl_releases/darwin/arm64/latest": dial tcp: lookup api.fly.io on 192.168.2.254:53: no such host

For console ssh:

$ flyctl ssh console -c fly/environments/production/fly-production.toml

WARN failed querying for new release: Get "https://api.fly.io/app/flyctl_releases/darwin/arm64/latest": dial tcp: lookup api.fly.io on 192.168.2.254:53: no such host

Error get app: Post "https://api.fly.io/graphql": dial tcp: lookup api.fly.io on 192.168.2.254:53: no such host

Am I missing something? Is there an outage?

1 Like
2

Works again now…

3

Hey, I’m sorry that you were experiencing issues with flyctl. We were noticing some issues with connections to wireguard peers that may have been related. We’re currently investigating, do you happen to know what gateway/region your flyctl instance is connecting to?

You can find this info by running cat on this file: ~/.fly/config.yml

4

endpointip: ams1.gateway.6pn.dev

1 Like
5

Happening again right now…

flyctl ssh console -c fly/environments/production/fly-production.toml
WARN failed querying for new release: Get "https://api.fly.io/app/flyctl_releases/darwin/arm64/latest": dial tcp: lookup api.fly.io on 192.168.2.254:53: no such host
Error get app: Post "https://api.fly.io/graphql": dial tcp: lookup api.fly.io on 192.168.2.254:53: no such host
6

This this happening for everybody? How can I access our servers?

7

So it looks like DNS on the flyctl side may have been stale, that is likely causing your connectivity issues. We’re actively troubleshooting this, you can keep track of the status here → https://status.flyio.net/

8

I’m trying again today, getting messages like last time. Is the problem the same again?

9

Error Post "https://api.fly.io/graphql": dial tcp: lookup api.fly.io on 192.168.2.254:53: no such host

10

Hi all, I’m also running into this problem. I’ve tried a few commands such as fly wireguard reset, but this also fails with error “no such host”.

The CLI is completely unusable :frowning:

11

This error actually means that flyctl is not even even make a DNS lookup on your local DNS server at 192.168.2.254. That address belongs to your router, which may have a flaky DNS server on it. This can happen for many reasons, so it’s preferable to use a reliable public DNS service like OpenDNS.

12

My god I think this is it. No idea what exactly was wrong, but I canged my macbooks dns lookup ip to 8.8.8.8 and it seems to work now… Thank so much.

1 Like