@weihsihu I’ve added the Organization associated with the whoseworld App.
My account is also affected from this change. Orgname: andre-932
Appname: letsglow
Please also exclude my account too - The plan change will first fake effect on 1. Jan.
Best Andre
I’ve added the Org to the exclusion list.
I’m also on the legacy hobby plan and having issues with deployment. Can You exclude me as well? Appname is palsimen-books
I would be really grateful if you could exclude me as well. I need to deploy the new version of my app as soon as possible.
Thanks for the suggestion. Unfortunately, the --depot
flag doesn’t appear to change anything at all for me. The output and error in the console are exactly the same. I also verified that I am running a recent version of flyctl:
flyctl v0.3.55 linux/amd64 Commit: 2e7e50db83543036a920499d6dba43b93fb4f085 BuildDate: 2024-12-26T14:32:20Z
This is running inside WSL2+Ubuntu.
@palsimen and @dominikw I’ve added your Orgs to the exclusion list.
@Styrke I’m out of ideas but will post the issue internally to see if anyone else has ideas.
Hi, I am getting the same error.
Hey hovancik, I’ve added your organization to the exclusion list.
Hey @Styrke,
flyctl should force the builder’s region if FLY_REMOTE_BUILDER_REGION
envvar is set.
First locate the builder’s app (if you haven’t switched to depot yet) and destroy it. Use a combination offly apps list
and fly apps destroy
.
Then deploy the app with:
FLY_REMOTE_BUILDER_REGION=ams fly deploy
@dangra I’m also running into this. Could you add my app folderling to the list, too?
Just ran into this, error messages definitely need work here, it would make sense to just tell me I’m on legacy and that’s why the region scale didn’t work.
I’ve upgraded but it’s telling me I have to wait until Feb 1st, is there any way I can speed this up outside of moving my infra to a new account? that would be one hell of an annoying hack to get our systems scaled into a couple more regions.
@manukall @Southclaws I think you both should be good now. Let me know otherwise. thanks
Hey @Southclaws, after your suggestion, soon you will see a new and hopefully clearer message. It will go in the next rollout. thanks!
I’m getting the same error:
Region ‘fra’ cannot host your machine
If I’m eligible, would you be willing to add me to the exclusion list too please?
Perfect, thanks! Deployed to FRA region successfully!
Also, unrelated but I’m wondering where in Frankfurt the DC is and what the potential latency to the AWS facilities are? I ask since my database is there (hence the move, annoyingly can’t move the DB to London due to some technical outage on their side)
I’m also running into this. Could you add my app “ksu” (organization “jan-529”) to the list, too?
I’ve encountered this problem while restarting my app the old way (scale down to 0 then back to 1). Appreciate it if you can exclude my org till you decide on what to do. Thanks.
Executing scale plan? (y/N) y Error: failed to launch VM: Region 'fra' cannot host your machine because your organizaion is on a legacy or non-paid plan. Please upgrade your plan or use an alternative region (see `fly platform regions`). (Request ID: 01JGZBK2Q71Q1Q5MXG2B3JK1XD-arn)
Sorry for the delayed responses for the last little bit here. Once we were all back from holiday break, we decided to remove the restriction for the fra
region to allow our legacy “hobby” plan access. We’ll update the thread again once we remove the overrides in place that were added for those who requested it.
Well that doesn’t seem to really work then:
Verifying if app can be safely deployed
Creating green machines
Rolling back failed deployment
Error: failed to launch VM: Region 'fra' cannot host your machine because your organizaion is on a legacy or non-paid plan. Please upgrade your plan or use an alternative region (see `fly platform regions`).
failed to create green machines (Request ID: 01JH3BHRHSBN3BYXGP1QA57KD4-waw) (Trace ID: f99a450b67b9bd0ee2411815690065ee)
So is there even any non-premium alternative region, or is that just a wrong message and the hobby plan is being disposed entirely, with people being left on confusing error with no prior warning?