When deploying on fly, server PORT is set to 8080 instead of 3000?

[Martinsos]

We had two users encounter this situation. It is not clear how that happened -> they used wasp deploy fly deploy and that should have set PORT to 3000, not 8080. We should investigate to figure out what could be causing this.

One noticable thing is that on the first deploy one of the users forgot some other env vars, so they redeployed a couple of times till they got them all set correctly. Might it be that in this process, PORT somehow got messed up? Or it was never set to 3000?

Related discord convo: https://discord.com/channels/686873244791210014/1313215934844113000/1313215934844113000 .

[vincanger]

This just happened to me as well:

1. Ran wasp deploy fly launch cursor-template ams --org wasp
2. Encountered the following error:

$ flyctl postgres create --name cursor-template-db --region ams --vm-size shared-cpu-1x --initial-cluster-size 1 --volume-size 1 --org wasp
/bin/bash: flyctl: command not found
🚀  There was an error running "wasp deploy fly create-db <region>". Please review the error and try again (if appropriate). 

3. Ran wasp deploy fly create-db ams and encountered error that I forgot to add the org slug so
4. Ran wasp deploy fly create-db ams --org wasp && wasp deploy fly deploy --org wasp
5. Checked port and it was set to 8080 so I changed it to 3000 and it worked and is now live at https://cursor-template-client.fly.dev/

[Martinsos]

Hm ok we certainly have to look into this then! Btw what do you think caused that first error, any ideas? Ok so you ran "launch" -> and that error popped out at which moment? Woudl would it say that command is not found hm. What is your version of flyctl?

[vincanger]

Fly at the time was having an issue so perhaps the db creation and app deployment overall failed because of that? Hard to say.

Not at my laptop now but I believe I’m on the latest flyctl version.

[jturner]

I also just ran my first wasp deploy fly launch ptcgp-friends ord for my app and had the same issue where the server was running on 8080 but fly.io wanted it on 3000. I ran wasp deploy fly cmd secrets set PORT=3000 --context=server to fix this.

Otherwise I encountered no other errors when running the launch command.