Railway Deployment #2956f8 fix: bind Uvicorn to 0.0.0.0#194
Merged
Conversation
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.
Problem
Uvicorn was bound to
--host ::(IPv6), but Railway's healthcheck proxy connects via IPv4. The container's network stack did not route IPv4 healthcheck requests to the IPv6-bound socket, causing all 7 healthcheck attempts to return "service unavailable" with zero HTTP requests reaching the app.Solution
Changed
--host ::to--host 0.0.0.0in the Dockerfile CMD so Uvicorn listens on all IPv4 interfaces. This matches Railway's requirement that apps bind to0.0.0.0:$PORTfor healthchecks to succeed.Changes
backend/DockerfileContext
02e4d3bGenerated by Railway