[New date] We are going to start charging for dedicated IPv4 in ~~January 1st~~ starting February 1st

Fresh Produce
61

I try to update and this is what I get:

# flyctl version update                                                                                                                                                                                                  Update available 0.0.429 -> v0.1.136.
Run "flyctl version update" to upgrade.
/bin/bash -c
Running automatic update [curl -L "https://fly.io/install.sh" | sh]
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  1735    0  1735    0     0   7006      0 --:--:-- --:--:-- --:--:--  7024
######################################################################## 100,0%
set update channel to shell
flyctl was installed successfully to /home/socrates/.fly/bin/flyctl
Run 'flyctl --help' to get started
# flyctl version
Update available 0.0.429 -> v0.1.136.
Run "flyctl version update" to upgrade.
flyctl v0.0.429 linux/amd64 Commit: 6db701e0 BuildDate: 2022-11-04T13:45:42Z

is not actually updating the version

62

I did

brew upgrade flyctl

and that worked

63

The IP usage graph needs some TLC. It’s missing values on each axis: I’m guessing number of requests on the y and dates on the x. Without it, it just looks like a blob.

64

We’ve just added axes and fixed the tooltip that we used to have on these graphs!

65

I’ve just noticed the ‘7 distinct IPv4 - $14.46’ in the current invoice, apparently they are for very old apps in a suspended state. fortunately the charge was unsuccessful. Do I have to worry about this and contact the billing team?
I’ll go ahead and remove these 7 IPs for now.

66

Thanks. There’s still an undefined lying around (for period? month?):
Average Over last undefined

67

I just pushed a fix for this about an hour ago, it should show “1 month”.

edit: oops, I haven’t yet actually pushed. Will do so soon!
edit 2: now pushed

1 Like
68

I’ve just verified and your invoice was voided (meaning no need to pay) because the only charge was IPv4.

1 Like
69

Just wanted to update everyone that we pushed back the date to a month. Here’s what happened:

  • We refunded/credited everyone or voided invoices if they were unpaid and the only charge was Dedicated Anycast IPv4 for this month.
  • We brought back the preview charge on your invoice, it will be there for this entire January so you can spot sources of dedicated IPv4 bills
  • We are not going to send charges for IPv4s in anyone’s invoices on February 1st, take your time to switch from dedicated to shared over this month.
  • Starting February 1st we will collect charges over the month and the first invoice that will bill those will be March 1st
  • I’ve updated this topic accordingly, let me know if something feels weird.
  • Everyone with a Dedicated IPv4 was just emailed.

Let me know if there’s any questions or if something wasn’t clear so we can better word it!

70

Just a small comment: We tried to update our hobby app (“bg”) to a shared IP using the given commands.

Oddly, all subsequent deploys failed ("error.message=“could not find a good candidate within 90 attempts at load balancing. last error: no known healthy instances found for route tcp/443.”)

After re-adding a dedicated IP, deploys instantly worked again.

Haven’t gotten around to debugging, but just a heads up that the change might not always be uneventful :slight_smile:

EDIT: OR IT’S BAD TIMING AND Fly.io Status - Increased registry latency

71

I accept that my post got kinda lost in all the posts about comms and billing so I left it a few days for that to cool down.

Would it be possible to get a response to the question:

Can you give a bit more info about the tradeoffs of using a shared vs dedicated IP?

In particular, how this applies to outbound traffic from machines. If my application calls out to APIs that apply rate limits by IP address and I switch from a dedicated to a shared ipv4, am I now essentially sharing rate limit quota with other fly customers sharing the same IP that call out to that same API?

Thanks

72

I’m trying to create a shared ipv4, but it says that I can’t due to an wildcard. Is there any place that I can found more information about this? I’m do not have much knowledge about this

73

I have no idea where the wildcard is configured on fly.io, tried to find but without success.

 flyctl ips allocate-v4 --shared
Error: cannot use a shared ipv4 with wildcard hostnames, please remove those before allocating a shared IP: *.<<mydomain>>.com.br
74

In “Certificates” for your app, you should have a wildcard cert that is the issue. At least I think thats the issue you are encountering.

1 Like
75

Thanks!!

1 Like
76

Np pal :+1:

77

Currently, Dedicated vs Shared IP (i.e. this topic) has no bearing on outbound IP address.

2 Likes
78

Running into the same issue, but I do actually need the wildcard certs. I guess this means I need to pay up for the dedicated IP?

Not a great situation since wildcard certs are advertised as $1/month, but looks like now there’s an additional hidden fee of $2/month for the dedicated IP, which really changes the unit economics.

Is there a technical blocker for bringing wildcard cert support to shared ipv4, or is it just a prioritization thing? If it’s the latter I’d like to see the billing for dedicated ipv4s delayed until wildcard certs for shared ipv4 are available.

79

I don’t have the impression that this is IP “usage”. I removed my static IP from my DNS config several days ago so no-one should hit it but it still shows 1 here. It looks to me that it’s IP “reservation” and not “usage”.

80

We’ve just added a button to the web dashboard to release an IP assignment.

If you go to https://fly.io/apps/APP_NAME, you should see a list of assignments and a button next to each to release the IP.