johan
/
mission-control
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fix: prefer explicit public gateway websocket url (#325)

This commit is contained in:
jonboirama 2026-03-14 17:32:28 +10:00 committed by GitHub
parent 863c100e66
commit b5d44df705
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/app/api/gateways/connect/route.ts
View File

@ -174,9 +174,14 @@ export async function POST(request: NextRequest) {
return NextResponse.json({ error: 'Gateway not found' }, { status: 404 }) return NextResponse.json({ error: 'Gateway not found' }, { status: 404 })
} }
// Prefer an explicitly configured browser WebSocket URL when provided.
// This is required for reverse-proxy setups where the browser-facing gateway
// lives on a different host/path than the server-side localhost gateway.
const explicitBrowserWsUrl = String(process.env.NEXT_PUBLIC_GATEWAY_URL || '').trim()
// When gateway host is localhost but the browser is remote (e.g. Tailscale), // When gateway host is localhost but the browser is remote (e.g. Tailscale),
// resolve the correct browser-accessible WebSocket URL. // resolve the correct browser-accessible WebSocket URL.
const remoteUrl = resolveRemoteGatewayUrl(gateway, request) const remoteUrl = explicitBrowserWsUrl || resolveRemoteGatewayUrl(gateway, request)
const ws_url = remoteUrl || buildGatewayWebSocketUrl({ const ws_url = remoteUrl || buildGatewayWebSocketUrl({
host: gateway.host, host: gateway.host,
port: gateway.port, port: gateway.port,