valid fly.io regions not being accepted by wasp?
This one is really puzzling me. Not sure if I'm making a stupid mistake. lhr is a valid region which is marked as live on fly - have also tried other regions e.g. mia
wasp deploy fly launch worrried lhr$ flyctl version flyctl v0.3.144 darwin/arm64 Commit: 42cbb921deda9c446c6f7ea007a5f284c13afb8b BuildDate: 2025-06-17T17:07:34Z $ flyctl auth whoami ... 🚀 Invalid region code lhr. Please specify a valid 3 character region id: https://fly.io/docs/reference/regions 🚀 You can also run "wasp deploy fly cmd platform regions --context server". ❌ --- [Error] Deploy command failed: --------------------------------------------- Deploy command failed with exit code: 1
7 Replies
Hi @I’m not kidding. 🇵🇸🇮🇱. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources, the Wasp CLI expects a valid 3-character Fly.io region code when deploying (e.g.,
- Double-check the region code using the commands above. - If
- Deploying with the Wasp CLI: Fly.io Regions - Deploying with the Wasp CLI ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @I’m not kidding. 🇵🇸🇮🇱, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?
mia for Miami) and references the official Fly.io regions list for valid codes. The error message you received—"Invalid region code lhr. Please specify a valid 3 character region id"—suggests that the CLI is not recognizing lhr (London) as valid, even though it is listed as live on Fly.io.
The documentation confirms that you should use 3-character region codes and that you can list all available regions with:
or
If you have confirmed that lhr is present in the output of these commands and still receive the error, the knowledge sources do not provide a direct solution or explanation for this issue. There is no mention of region code mismatches or bugs in the Wasp CLI regarding region validation in the provided documentation.
In summary:- Double-check the region code using the commands above. - If
lhr is listed but still not accepted, this may be a bug or a temporary inconsistency between Fly.io and Wasp CLI.
- The knowledge sources do not contain enough information to explain why a valid region code like lhr would be rejected by the Wasp CLI.
You may want to open an issue on the Wasp GitHub or ask in the Wasp Discord for further assistance, as this could be an edge case or a recent change not yet reflected in the CLI or documentation.
References:- Deploying with the Wasp CLI: Fly.io Regions - Deploying with the Wasp CLI ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @I’m not kidding. 🇵🇸🇮🇱, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?
Wohooo @I’m not kidding. 🇵🇸🇮🇱, you just became a Waspeteer level 2!
From
Amsterdam, Netherlands ams ✓ ✓ 1561
Bucharest, Romania otp 282
Frankfurt, Germany fra ✓ 1259
London, United Kingdom lhr ✓ 3598
Paris, France cdg ✓ 1088
Stockholm, Sweden arn 563
Warsaw, Poland waw 591 @kapa.ai
flyctl platform regions command:
EuropeAmsterdam, Netherlands ams ✓ ✓ 1561
Bucharest, Romania otp 282
Frankfurt, Germany fra ✓ 1259
London, United Kingdom lhr ✓ 3598
Paris, France cdg ✓ 1088
Stockholm, Sweden arn 563
Warsaw, Poland waw 591 @kapa.ai
Let me check the knowledge base for you again. One moment! :books:
----------------------
Based on the knowledge sources, the Wasp CLI expects you to use valid 3-character Fly.io region codes, such as
-
lhr for London, when deploying your app. The documentation specifically instructs users to find available regions by running flyctl platform regions and to use those codes in commands like:
If you are using lhr (which is shown as valid and live in your flyctl platform regions output) and Wasp still reports it as invalid, the knowledge sources do not provide an explanation or workaround for this issue. There is no mention of region code mismatches or known bugs in the Wasp CLI regarding region validation in the provided documentation.
Therefore, if you have confirmed that lhr is a valid region code and it is still not being accepted by Wasp, this may be a bug or an inconsistency between the Wasp CLI and Fly.io. The knowledge sources do not contain enough information to resolve this issue directly. You may need to reach out to the Wasp team via GitHub or Discord for further assistance, as suggested in the documentation for similar deployment issues Deploying with the Wasp CLI: Fly.io Regions.
Summary:-
lhr is a valid region code according to Fly.io.
- Wasp CLI should accept it, but if it does not, the knowledge sources do not provide a solution or explanation.
- Further support from the Wasp team may be required.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @I’m not kidding. 🇵🇸🇮🇱, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?any mention of this issue for specific wasp versions? currently running 0.15.0 @kapa.ai
Let me check the knowledge base for you again. One moment! :books:
----------------------
I'm sorry, but the knowledge sources do not contain any information about this specific Fly.io region code issue being related to particular Wasp versions, including version 0.15.0. There are no mentions of region validation bugs or incompatibilities tied to specific Wasp releases in the provided documentation or support threads. If you suspect this is a version-specific bug, it may be best to report it to the Wasp team or check for open issues on their GitHub.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @I’m not kidding. 🇵🇸🇮🇱, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
update: fixed it upgrading to wasp 0.16.6