W
Waspβ€’4mo ago
Kbk

FLY deploy WASP 13.2 Issue

Hello today i tried to deploy app using wasp deploy fly launch appname ams Firstly i for prompted thati need to specify organization so i used wasp deploy fly launch otcdesk ams --org personal than whatever region i put i got this error kubik@KBK:/mnt/c/Users/patku/projects/otcdesk/kantor$ wasp deploy fly launch otcdesk fra --org personal $ flyctl version flyctl v0.3.137 linux/amd64 Commit: 7a200d0547f773b3892a907959878b278d04f107 BuildDate: 2025-06-02T21:28:41Z $ flyctl auth whoami patkub911@gmail.com πŸš€ Invalid region code fra. 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: ---------------------------------------------
Fly
Regions
Documentation and guides from the team at Fly.io.
5 Replies
kapa.ai
kapa.aiβ€’4mo ago
Hi @Kbk. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- The error message you received:
πŸš€ Invalid region code fra. 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".
indicates that the region code fra is not recognized as a valid Fly.io region code. According to the Wasp documentation, you must use a valid 3-character region code supported by Fly.io. To find the correct region codes, you should run:
flyctl platform regions
flyctl platform regions
or, as suggested in the error message:
wasp deploy fly cmd platform regions --context server
wasp deploy fly cmd platform regions --context server
This will list all available regions you can use for deployment. Make sure to pick a region code exactly as listed in the output of these commands. For more details, see the documentation on Fly.io regions. If you continue to have issues, double-check that you are using the correct region code and that your Fly.io CLI is up to date. The knowledge sources do not mention any issues specific to Wasp 0.13.2 regarding region codes, so this is most likely a region code typo or mismatch with Fly.io's current list of supported regions. Let me know if you need help finding the correct region code! ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @Kbk, 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?
Kbk
KbkOPβ€’4mo ago
yes I used this but no one region is working Europe Amsterdam, Netherlands ams βœ“ βœ“ 1923 Bucharest, Romania otp 105
Frankfurt, Germany fra βœ“ 1285 London, United Kingdom lhr βœ“ 1598 Madrid, Spain mad 278 Paris, France cdg βœ“ 999 Stockholm, Sweden arn 209 Warsaw, Poland waw 306 Im ussing correct working regions and still wasp is not taking that on account i have its my fly version:flyctl v0.3.137 linux/amd64 Commit: 7a200d0547f773b3892a907959878b278d04f107 BuildDate: 2025-06-02T21:28:41Z @Wasp Expert Any idea why wasp is not recognizing AMS as okay region? Okay i used old version of fly and its going thru now i got this erro Error org slug must be specified when not running interactively do you know which verion of FLY i can use with WASP 13.2 to have smooth launch XC? but now this error: πŸš€ Setting up server app with name otctest-server $ cd /mnt/c/Users/patku/projects/otcdesk/kantor/.wasp/build $ flyctl launch --no-deploy --name otctest-server --region ams --org personal Creating app in /mnt/c/Users/patku/projects/otcdesk/kantor/.wasp/build ⚠️ There was a possible issue setting up your server app. We tried modifying your server fly.toml to set min_machines_running = 1, but couldn't find the option min_machines_running in the fly.toml. We advise that you additionaly check what is the value for "minimal number of machines running" on Fly for this server app and confirm that it is set to the value you are OK with. Be aware that if it is set to 0, your server will shut down when there are no requests from the client, which might be an issue for you if you have recurring Jobs or some other processes that need to keep running on the server even without external input, in which case we advise keeping "minimal number of machines running" setting at a number larger than zero. Contact the Wasp Team at our Discord server if you need help with this: https://discord.gg/rzdnErX Press any key to continue or Ctrl+C to cancel. I will try FLY version from flyctl v0.3.72 linux/amd64 Commit: c0a61b8d482cf6e697ee184544280d1687883da8 BuildDate: 2025-01-30T15:46:06Z
Kbk
KbkOPβ€’4mo ago
GitHub
Release v0.2.90 Β· superfly/flyctl
Changelog 062495b Bump github.com/spf13/cobra from 1.8.0 to 1.8.1 (#3740) b2af9b6 build: upgrade docker/docker and buildpacks/pack (#3739) 3a45c71 Deprecate the Barman Machine (#3742) ac994f0 Bump...
MEE6
MEE6β€’4mo ago
Wohooo @Kbk, you just became a Waspeteer level 4!
Filip
Filipβ€’4mo ago
Hey @Kbk, can you update Wasp to a newer version. Wasp 0.13.2 is pretty old.

Did you find this page helpful?