Fly API error allocating IPv6 address

1

79bb8045776b: Pushed
2246e7a93200: Layer already exists
3309c4c92cd8: Layer already exists
1831bc7c29d8: Layer already exists
2527ef07978b: Layer already exists
27f1718f3cbc: Layer already exists
7b041ce47d02: Layer already exists
b2c3b7c27a5e: Layer already exists
1edb29200929: Layer already exists
11d265337641: Layer already exists
650abce4b096: Layer already exists
deployment-01GVWR6ZP0H83D40S1C6R6CN3T: digest: sha256:a5cf8f03baa1489588ae306b804493c749928b8b65aaf6e34523adbec9bd9848 size: 2627
→ Pushing image done
image: registry.fly.io/twilight-frost-6454:deployment-01GVWR6ZP0H83D40S1C6R6CN3T
image size: 308 MB
==> Creating release
Error You hit a Fly API error with request ID: 01GVWR8EREG07DVAWEC7GRM925-nrt

I’m having issues, I’ve been deleting, recreating and redeploy. I still see the same error :confused:

2 Likes
2

I’ve had the exact same issue. I checked the status page as a previous post suggested that but there isn’t anything indicating and issue there. I’ve also tried deploying from two locations and two apps, no luck

3

Same issue!

4

I also tried the same thing, no luck

5

I’m also running into the same issue :confused:

6

We just fixed a bug that was preventing IPv6 addresses from being assigned to new apps.

1 Like
7

→ Pushing image done
image: registry.fly.io/tadyuu:deployment-01GVWWVCYFZ87QYCRN6HWY8RJM
image size: 295 MB
==> Creating release
Error You hit a Fly API error with request ID: 01GVWWWBC83GQSM5J56920DM6M-hkg

8

Hello, we just found and fixed a bug that was preventing new apps from getting assigned IPV6 addresses.

9

Worked the first time, but now it won’t work at all…

image

1 Like
10

Yup…seeing this as well :frowning:

11

Seeing this as well right now trying to host a Docker container, deleting and recreating the app did not help.

12

Yeah, I keep getting this as well at the moment. I tried multiple times, including removing and starting again.

13

I’ve the same problem in WAW region with newly created app based on Docker.

You hit a Fly API error with request ID: 01GVWW402T6G23F1EAGQ8DET80-waw
14

Now I have this error :confused:

1 desired, 1 placed, 0 healthy, 1 unhealthy
→ v2 failed - Failed due to unhealthy allocations - no stable job version to auto revert to and deploying as v3

15

Got my app up and deployed now! Just had to use fly destroy then recreate it with fly launch. Completely deleting dockerfile and .dockerignore.

16

Woke up this morning, didn’t change anything. All I did was run flyctl deploy and it worked.

17

Yeah…no changes required. Clearly not on our end. Worked for me as well this morning.

18

The bug y’all were hitting was fixed, but I think the response got buried in the middle of the thread: Fly API error allocating IPv6 address - #6 by rugwiro

1 Like