Error failed creating volume: To create more than 1GB in volumes please add a payment method

I am testing out fly but seem unable to create a volume within the 3GB free plan limit, am I missing something here?

fly volumes create data_vol --size 1
1 Like

Same error, even though I only have 1 volume that is only 1gb in size. The free tier doc is pretty explicit about having a max of 3gb total.

1 Like

I’m having the same issue, but I dont think there’s anything else I can do other than just bumping the thread and saying “me too”?

Has someone found a solution for this? I am testing out fly and getting this same error.

How about creating it with less than 1GB and then using fly scale memory?

Update: size seems to be only in GB, but let me try and give you a proper answer.

@SamC have you added a payment method?
Because apparently I can’t even launch an app without a payment method now.

No, I haven’t added a payment method. I am first planning to test it and then go for the payment plan. Its very weird that you can’t even launch an app without a payment method, it works for me though. I am still struggling with this issue.

(https://community.fly.io/t/images-get-lost-after-few-minutes-of-inactivity-in-server-it-works-fine-in-development/15150)

This is my main problem, could you please have a look at it? Thanks

Accounts will require a credit card, primarily to prevent abuse. If you stay within the free allowances, then you won’t be charged.

More info about credit cards: How We Use Credit Cards · Fly Docs

Somehow related:
I have 3 orgs and one of them doesn’t have a payment method.
I cannot launch an app in the org without a payment method.

Right after I select the region (otp), I get this error:
Error: We need your payment information to continue! Add a credit card or buy credit: Sign In · Fly

In total, I have 1 app in one of the orgs that has a payment method.

Is this expected behavior?

Update: Even if I delete that app, meaning no apps at all, still get the same error.
Persists after changing region.

Apparently its solved when you create with fly volume create data -r <region> -s 1, the -s means for size, that is default 3 (fly volue -h)