Can't deploy the remix application to our cloud service.

[lili21]

it works well at my computer. But not after deploy to our cloud service. below is the error message

TypeError: Invalid URL
    at new NodeError (node:internal/errors:405:5)
    at new URL (node:internal/url:637:13)
    at createRemixRequest (/opt/bytefaas/toutiao/app/gdserver/node_modules/.pnpm/@[email protected][email protected][email protected]/node_modules/@remix-run/express/dist/server.js:74:13)
    at /opt/bytefaas/toutiao/app/gdserver/node_modules/.pnpm/@[email protected][email protected][email protected]/node_modules/@remix-run/express/dist/server.js:39:21
    at Layer.handle [as handle_request] (/opt/bytefaas/toutiao/app/gdserver/node_modules/.pnpm/[email protected]/node_modules/express/lib/router/layer.js:95:5)
    at next (/opt/bytefaas/toutiao/app/gdserver/node_modules/.pnpm/[email protected]/node_modules/express/lib/router/route.js:144:13)
    at next (/opt/bytefaas/toutiao/app/gdserver/node_modules/.pnpm/[email protected]/node_modules/express/lib/router/route.js:140:7)
    at next (/opt/bytefaas/toutiao/app/gdserver/node_modules/.pnpm/[email protected]/node_modules/express/lib/router/route.js:140:7)
    at next (/opt/bytefaas/toutiao/app/gdserver/node_modules/.pnpm/[email protected]/node_modules/express/lib/router/route.js:140:7)
    at next (/opt/bytefaas/toutiao/app/gdserver/node_modules/.pnpm/[email protected]/node_modules/express/lib/router/route.js:140:7)

After some dig in, I found the issue
After deployed to our cloud service, the resolveHost is [fdbd:dc01:b:90::28]:dc01, which isn't a valid URL.

the source code

remix/packages/remix-express/server.ts

Lines 96 to 98 in 2228ec3

	let resolvedHost = `${req.hostname}${port ? `:${port}` : ""}`;
	// Use `req.originalUrl` so Remix is aware of the full path
	let url = new URL(`${req.protocol}://${resolvedHost}${req.originalUrl}`);

[kiliman]

What is your cloud service? That seems like a hosting issue if it's passing an invalid host header.

[lili21]

our company's private service. Yeah, there are very complex network gateway and proxy before the request reach the server. I guess the header just be modified or lost.

[sergiodxa]

You could "fork" the Express adapter, as you can see in the code, everything is in one file, so you can copy it and do any change you may need to make it work, including using a mock resolvedHost

[lili21]

@sergiodxa I'll try it. Thanks.

[vladmiller]

We've got the same issue w/ remix in k8s container running behind AWS ALB.

[ConnorCallison]

Yep same here!