Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

When deploying steps/02-docker, fly-proxy can't reach app at port 3000

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
docker, typescript
Domain
backend, devops

Research direction

Read steps/02-docker/Dockerfile and steps/02-docker/app/index.ts, then run fly deploy for the tutorial step to reproduce the fly-proxy warning. Update the configuration so the app listens on the expected port and verify that deployment no longer reports the address warning.

Written by the indexing model from the issue text.

Description

$  fly  deploy
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

Solution:
In steps/02-docker/Dockerfile, add:

# set environment variables
...
ENV SERVER_PORT="3000"

In steps/02-docker/app/index.ts, change:

.listen(process.env.PORT...

to

.listen(process.env.SERVER_PORT...
Dominant language
TypeScript
Stars
70
Forks
6
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.