Happy path project never serves traffic #5
Comments
knksmith57
added a commit
to knksmith57/hello-fly
that referenced
this issue
Dec 19, 2023
Although the "Deploy via Dockerfile" quickstart docs suggest fly will default to :8080 and will automatically use an EXPOSEd port if set, the observed behavior is that :3000 is always used instead. Update Dockerfile to use :3000 and set the $PORT environment variable to ensure the application listens on the configured port. Resolves fly-apps#5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following the suggestion to use this repo, from the signin redirect page, I cloned and launched (deconflicting the name).
The project never served traffic, and viewing the logs, errored saying
2023-12-02T22:26:57Z app[5683d496c42468] sjc [info][ 4.310534] reboot: Restarting system error.message="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)" 2023-12-02T22:27:00Z proxy[328744dbee4e85] sjc [error]request.method="GET" request.id="01HGPA7F3Q77TZXQE7NZSY5DDX-sjc"Given that this repo offers an intro project it's frustrating that its code conflicts with (newer?) defaults for expected application behavior.
Additionally, the error formatting seems off, like newlines are passed through, or the body comes before the timestamp.
The text was updated successfully, but these errors were encountered: