Skip to content

fix(gateway): bind to IPv6 dual-stack for Railway private networking #227

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maakle merged 1 commit into from
Jun 1, 2026
Merged

fix(gateway): bind to IPv6 dual-stack for Railway private networking #227

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion apps/gateway/src/main.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,14 @@ async function main() {
});

const port = env.MCP_PORT;
serve({ fetch: app.fetch, port });
// Bind to IPv6 unspecified (::) so the socket accepts BOTH IPv4 and IPv6
// connections in dual-stack mode. Railway's private networking resolves
// service hostnames (e.g. `gateway.railway.internal`) to IPv6 addresses;
// the default `0.0.0.0` bind is IPv4-only and rejects them with
// ECONNREFUSED. Public ingress (Railway edge → container) still works
// through the dual-stack socket. Docker/compose and local dev are
// unaffected — `::` accepts loopback traffic on both stacks.
serve({ fetch: app.fetch, port, hostname: '::' });
logger.info({ port }, 'gateway listening');

// Flush queued PostHog events on graceful shutdown — otherwise the
Expand Down
Loading