Having dedicated ip v4 address without opting it for it

[Steinmetz]

I had an old deploy lying around from 2022. I haven’t been billed for it ever. I went to my dashboard just now and clicked on the URL. All of a sudden I’m seeing a billing sum of 2$.

fly ips list
VERSION IP TYPE REGION CREATED AT
v4 123123 public global 2022-10-19T14:16:44Z
v6 123123:1234 public global 2022-10-19T14:16:47Z

I thought I could fix it with fly ips allocate-v4 --shared

But now I just have an additional shared IP:

fly ips list
VERSION IP TYPE REGION CREATED AT
v4 123 public global 2022-10-19T14:16:44Z
v6 123:1234 public global 2022-10-19T14:16:47Z
v4 1234 public (shared)

Not sure how to remove the dedicated one.

[lubien]

Jerome shared a guide on how to have zero downtime migrating from dedicated to shared IPv4 in case you have certificates:

We are going to start charging for dedicated IPv4 in January 1st

An update: We now allow having both a shared IPv4 and dedicated IPv4. This change should make it possible to switch to a shared IPv4 without downtime. The produce looks like this: Add shared ipv4 via flyctl ips allocate-v4 --shared (Optional: add the shared ipv4 as an A record for your hostname if you don’t use a CNAME to .fly.dev) Confirm your app works via shared IP: curl -Iv http://<your-hostname> --resolve <your-hostname>:80:<shared ipv4 you got> (should respond with a 301 redirect) Wait …

[jerome]

fly ips release and passing the IP you don’t want should do the trick!

[Steinmetz]

Thanks guys!

P.S.: Do I get my 2 bucks back?

[mealmond]

Hi
I hvae just come across this issue, is there a basic way to show me how to remove the dedicated IPv4 for the app I am using. I don’t have much in the way of IT skills, have read the article but got nowhere.

Is there a simple command line I can use and just add in the name of my app.

Many Thanks

Martin

[ditsuke]

Can attest to never having signed up for a dedicated ipv4 and getting billed $6 without any warning. It’s not much, but it’s very disappointing.

[mhoggard]

Be forewarned – if you don’t have a credit card associated with your account, you will not be able to allocate a shared IP. I was able to release – which immediately took my API offline – then when I tried to allocate, I got hit with an error stating I had to enter a credit card or purchase credits to proceed. Since I had already released the previous IP, breaking my site, I had no choice but to enter a credit card, which makes me very nervous.

Given that I’m supposed to be on a completely free plan and just got this surprise billing, not having entered a card was the one thing protecting me from this kind of situation. And now that’s gone, with no assurances that this won’t happen again.