Fix nginx upstream resolution for backend proxy#20
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
Nginx fails to start with "host not found in upstream "backend.railway.internal"" because
proxy_pass ${BACKEND_URL}causes nginx to resolve the upstream hostname eagerly at startup, before Railway's internal DNS is ready.Solution
Added
set $backend_url ${BACKEND_URL};inside both the/apiand/socket.iolocation blocks and changedproxy_passto use$backend_url. Whenproxy_passreceives a variable instead of a literal URL, nginx skips the startup-time DNS resolution and resolves the hostname on each request, by which point the internal Railway DNS is available.Changes
my-app/nginx.confGenerated by Railway