Server misbehaving

Questions / Help
1

Hello !

I am currently trying to deploy my app but i got this error :

Error: failed to fetch an image or build from source: error rendering push status stream: Get "https://registry.fly.io/v2/": dial tcp: lookup registry.fly.io on [fdaa::3]:53: server misbehaving

Can someone help me please ? :smiley:

2 Likes
3

is it still happening? @Surowyn

4

yes

5

I have the same issue. Could it be related to the migration to V2 apps? I also updated the old config as suggested in the email.

6

Same problem on a brand new app:

Error: failed to fetch an image or build from source:
error rendering push status stream: 
Get "https://registry.fly.io/v2/": 
dial tcp: lookup registry.fly.io on [fdaa::3]:53: 
server misbehaving
7

Same issue on AMS, with a V2 apps (not newly created or migrated).

8

same issue also on AMS, with 2 V2 apps.
Error: failed to fetch an image or build from source: error rendering push status stream: Get "https://registry.fly.io/v2/": dial tcp: lookup registry.fly.io on [fdaa::3]:53: server misbehaving

9

I just tried recreating the config, deleting and recreating the app, deleting the builder and recreating, none worked.

10

Any solution from the Fly team would be greatly appreciated so Iā€™ll try tagging some folksā€¦
@jsierles @JP_Phillips @jssjr @billy

11

This should hopefully be fixed now, can you try again?

12

Still the same issue as before (for me at least).

13

@lillian It has not been fixed unfortunately for me, same issue, hopefully you guys figure it out asap.

14

I face the same issue where I get

failed to fetch an image or build from source: error rendering push status stream: Get "https://registry.fly.io/v2/": dial tcp: lookup registry.fly.io on [fdaa::3]:53: server misbehaving
15

Still not fixed for me either

16

Iā€™m seeing the same error too.

17

Just tried. Still not working !

18

Hello, I still have the same issue here while trying to deploy a new app : ā€œError: failed to fetch an image or build from source: error rendering push status stream: Get ā€œhttps://registry.fly.io/v2/ā€: dial tcp: lookup registry.fly.io on [fdaa::3]:53: server misbehavingā€

19

Iā€™m also having the same issue. Yesterday was my very first day using fly.io, thatā€™s quite a bad first impression tbh.

20

Iā€™ve also had the same issue for the last 24 hours.

The image builds fine and if I run flyctl deploy --build-only the command finishes successfully.

However, regular flyctl deploy results in the same message as reported in the first post:

--> Building image done
==> Pushing image to fly
The push refers to repository [registry.fly.io/myapp]
Error: failed to fetch an image or build from source: error rendering push status stream: Get "https://registry.fly.io/v2/": dial tcp: lookup registry.fly.io on [fdaa::3]:53: server misbehaving
21

Iā€™m also having the same issue. I migrate one of my app to V2 and now i canā€™t deploy:

--> Building image done
==> Pushing image to fly
The push refers to repository [registry.fly.io/myapp]
Error: failed to fetch an image or build from source: error rendering push status stream: Get "https://registry.fly.io/v2/": dial tcp: lookup registry.fly.io on [fdaa::3]:53: server misbehaving