What exactly is making this test project transition from a “free plan, experiment, see what works” into a “you are trying to use pro features”?
Flyctl report:
…snip…
=> => pushing manifest for registry.fly.io/tnext-from-codespaces:deployment-01J9N88ECQXJGKWCPJC4AX7WSV@sha256:b3 0.4s
→ Build Summary: ()
→ Building image done
image: registry.fly.io/tnext-from-codespaces:deployment-01J9N88ECQXJGKWCPJC4AX7WSV
image size: 399 MBWatch your deployment at Sign in to Your Account · Fly
Provisioning ips for tnext-from-codespaces
Dedicated ipv6: 2a09:8280:1::49:d853:0
Shared ipv4: 66.241.124.154
Add a dedicated ipv4 with: fly ips allocate-v4This deployment will:
- create 1 “app” machine
No machines in group app, launching a new machine
-------
Failed: error creating a new machine: failed to launch VM: machines are disabled for this organization
-------
Error: error creating a new machine: failed to launch VM: machines are disabled for this organization (Request ID: 01J9N8AD5Y8X29APDDPKYG0EBT-lga) (Trace ID: f54a87dbc05ac946a49cd04210113127)
The most recent similar thread on this is failed to launch VM: machines are disabled for this organization, which says this error is related to not having a credit card linked to my account.
I’m confused about the current pricing structure – is there is no longer a free tier?
My dashboard says I’m on “Legacy Hobby plan - Great for side projects, test environments, or just learning how to use Fly.io. Run basic full-stack apps for free, and pay-as-you-go as your project grows.” [emphasis added]
I’m fine with there being features that require money, I just want to know where the dividing lines are. I have no idea how much or how little the things I’m contemplating might cost and I don’t want to link a credit card until I have a handle on that.
(edited to link to the fly-io branch in the repo, show most recent failure log, remove extraneous info, and collapse ‘string of replies’ into single edited post, as per Discourse suggestion.)