Yet, when I run fly deploy, I see that warnings that fly-proxy will not be able to reach my services because it’s still looking for port 3000:
WARNING The app is not listening on the expected address and will not be reachable by fly-proxy.
...
You can fix this by configuring your app to listen on the following addresses:
- 0.0.0.0:3000
And in my fly logs, I see:
instance refused connection. is your app listening on 0.0.0.0:3000? 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)
Am I missing some other config? I’ve tried manually scaling the machine count to 0 and back up.
Hi @flea, nothing’s really coming to mind, but a shot in the dark since there are no other responses: is the number 3000 really not in your fly.toml anywhere? e.g. in an http_service block populated on launch?
So I thought perhaps fly is looking at my Dockerfile and somehow assuming the port should be 3000? But that doesn’t make too much sense, because I’d imagine internal_port directly controls which port fly should be looking for.
Oh, I solved the problem - it was a silly mistake. I was using the command:
fly deploy --app my-app
when I should have been using:
fly deploy --config my-app.toml
The former command works for everything other than toml changes, so I’ve gotten in the habit of mindlessly using the former. Thanks for the reply @catflydotio