Server listen addr when deploying to fly.io

I'm on MacOS using wasp 0.13.0. For some reason when my server deploys (both with

wasp deploy fly deploy

wasp deploy fly deploy

and the manual fly deployment

flyctl deploy --remote-only --config ../../fly-server.toml

flyctl deploy --remote-only --config ../../fly-server.toml

I'm getting an errors about it not listening on the proper addr/port?

[error][PC01] instance refused connection. is your app listening on 0.0.0.0:8080? make sure it is not only listening on 127.0.0.1 (hint: look at your startup logs, servers often print the address they are listening on)
...
[info]waiting for machine to be reachable on 0.0.0.0:8080 (waited 10.399511506s so far)
...
[error][PM05] failed to connect to machine: gave up after 15 attempts (in 12.400552411s)

[error][PC01] instance refused connection. is your app listening on 0.0.0.0:8080? make sure it is not only listening on 127.0.0.1 (hint: look at your startup logs, servers often print the address they are listening on)
...
[info]waiting for machine to be reachable on 0.0.0.0:8080 (waited 10.399511506s so far)
...
[error][PM05] failed to connect to machine: gave up after 15 attempts (in 12.400552411s)

Everything works as expected locally. I've run

wasp clean

wasp clean

and done clean deploys both manually and using the wasp deploy wrapper with no luck. I can't see any changes I made that would affect this, any ideas?

Wasp•2y ago•

32 replies

ellie

Server listen addr when deploying to fly.io

I'm on MacOS using wasp 0.13.0. For some reason when my server deploys (both with

wasp deploy fly deploy

wasp deploy fly deploy

and the manual fly deployment

flyctl deploy --remote-only --config ../../fly-server.toml

flyctl deploy --remote-only --config ../../fly-server.toml

I'm getting an errors about it not listening on the proper addr/port?

[error][PC01] instance refused connection. is your app listening on 0.0.0.0:8080? make sure it is not only listening on 127.0.0.1 (hint: look at your startup logs, servers often print the address they are listening on)
...
[info]waiting for machine to be reachable on 0.0.0.0:8080 (waited 10.399511506s so far)
...
[error][PM05] failed to connect to machine: gave up after 15 attempts (in 12.400552411s)

[error][PC01] instance refused connection. is your app listening on 0.0.0.0:8080? make sure it is not only listening on 127.0.0.1 (hint: look at your startup logs, servers often print the address they are listening on)
...
[info]waiting for machine to be reachable on 0.0.0.0:8080 (waited 10.399511506s so far)
...
[error][PM05] failed to connect to machine: gave up after 15 attempts (in 12.400552411s)

Everything works as expected locally. I've run

wasp clean

wasp clean

and done clean deploys both manually and using the wasp deploy wrapper with no luck. I can't see any changes I made that would affect this, any ideas?

Continue the conversation

Join the Discord to ask follow-up questions and connect with the community

Wasp

Rails-like framework for React, Node.js and Prisma. Build your app in a day and deploy it with a single CLI command.

4,603 Members

Join

Server listen addr when deploying to fly.io

Server listen addr when deploying to fly.io

Continue the conversation

Wasp

Continue the conversation

Wasp

Similar Threads