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

Fresh Produce
41

I’m one of the people with a sub-$5 card charge.

It’s not about the $2, or the “shouldn’t be billed if it’s under $5” - we shouldn’t be getting billed at all without pre-warning. As someone who doesn’t visit the forum, I was never notified IP’s would become chargeable.

Will you be doubling the bandwidth charges without warning us? Trippling the VM costs once there’s a fleet deployed - and only letting us know once the bill’s generated? That’s the worry now.

1 Like
42

Yeah, you’re right! We messed up here in various ways, and we’re working right to to issue refunds for this charge across the board.

For users who are stuck not being able to issue shared IPs - we’re rolling out a fix to allow that while we work on the refund.

Finally: we had scheduled an email to notify users about this, but that never happened. So for future billing changes, we’ll definitely make sure users are notified ahead of time.

4 Likes
43

Sorry for asking.

If I do nothing, I get some $ / ip on the invoice, but everything works as it has so far, and I can continue doing nothing, yes?
Because that would be what I want for now and the next time. Everything just works as it did. And I am okay with finally paying you for your excellent service.

2 Likes
44

Yes, you can keep your dedicated IP if you prefer. The January charge will be reverted, and you’d be charged in February.

The migration process to shared IPs is simple, if you ever want to do it later!

1 Like
45

I’m adding my voice to the ones who already mentioned this. I’m willing to bet that like 1% of users are following these threads, and 99% got a surprise email about some charges they’ve never heard of.
This should have been advertised by email months ago, with clear instructions on how to switch to shared IPs, so that users who don’t care about fixed IPs can keep using a free tier.

46

Please update the doc with this. The docs still says:
This command will fail if the app has a dedicated IPv4 address.

1 Like
47

Update: most unbilled charges have already been reversed. That means any accounts without cards will not need to add them. Those accounts can start transitioning to shared IPs, if desired.

Tomorrow, we’ll issue credits for accounts that had real charges billed to a card.

Also, the latest release of flyctl should more clearly indicate which IPs are dedicated, and that they incur a cost:

$ flyctl ips list -a myapp
VERSION	IP                                  	TYPE                     	REGION	CREATED AT
v4     	137.66.3.38                         	public (dedicated, $2/mo)	global	Dec 16 2022 11:56
v6     	2a09:8280:1::4f68                   	public (dedicated)       	global	Jul 5 2022 20:13
v6     	fdaa:0:22b7:0:1::2                  	private                  	global	Jul 5 2022 20:14
4 Likes
48

You would need to release the dedicated IP address before grabbing the shared IP address.

49

@joshua-fly

Also, the latest release of flyctl should more clearly indicate which IPs are dedicated, and that they incur a cost:

Yes! :slight_smile: That public (dedicated, $2/mo) is much clearer.

1 Like
50

Could you please clarify this?
I am travelling without my computer so i can’t install a command line tool to fix these unexpected charges. When i log into fly, following this link, i don’t see any “launch webcli” button!
Using chrome on android.

51

You should add this to the OG post. Probably at the top, since this are the most common instructions people will need.

1 Like
52

Good idea. Ive updated it to include these instructions

1 Like
53

Thats not what the top post now says, this issue has been fixed. And I can attest that I was able to get a shared address while having a dedicated one.

54

fly ips release 213.188.197.238 -a (app_name)
Error: Could not find IPAssignment

55

Is it possible to remove a dedicated IPv4 from Web UI? The aforementioned Web CLI/Terminal doesn’t seem to be a thing anymore.

56

@joshua-fly Yep, all good! That was the case and thank you for for sorting it all out :slight_smile: The eventual email was thorough and good to see. All the best,

57

If you do fly ips list -a (app_name) is that IP there? I can’t see it from my end on your org.

58

I am getting this error:

fly ips allocate-v4 --shared -a destro-sample-app
Error: unknown flag: --shared
Usage:
  flyctl ips allocate-v4 [flags]

Flags:
  -a, --app string      Application name
  -c, --config string   Path to application configuration file
  -h, --help            help for allocate-v4
  -r, --region string   The target region (see 'flyctl platform regions')

Global Flags:
  -t, --access-token string   Fly API Access Token
  -j, --json                  json output
      --verbose               verbose output

Error unknown flag: --shared
59

@Destrozates It’s possible you’re on an old version of flyctl. The latest is v0.1.136.

60

We finished sending credits to the remaining accounts!