Fix 502 on Railway: expose 8080#138
Merged
Merged
Conversation
k7cfo
pushed a commit
to k7cfo/railclaw
that referenced
this pull request
Feb 21, 2026
0xRichardH
pushed a commit
to 0xRichardH/openclaw-railway-template
that referenced
this pull request
Feb 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #132.
Railway commonly routes to the port it detects from the image (EXPOSE) / service networking settings.
Our wrapper listens on Railway’s injected
PORT(often 8080), but the Dockerfile was exposing 3000, which can cause Railway to route to the wrong port → 502 even though logs show the wrapper listening.Changes:
EXPOSE 8080Tests:
npm test