getRequestEvent().clientAddress returns undefined in production when using @solidjs/vite-plugin-nitro-2, despite working in dev.

Root Cause

The virtual entry bridging Nitro (h3 v1) → solid-start (h3 v2) was:

import { fromWebHandler } from 'h3'
import handler from '${ssrEntryFile}'
export default fromWebHandler(handler.fetch)

Three things combine to drop the IP:

1. h3 v1's fromWebHandler calls handler(toWebRequest(event), event.context) — toWebRequest produces a plain Request with no IP metadata
2. h3 v2's H3Core.fetch(request) ignores the second argument, so the context is never passed through
3. h3 v2's getRequestIP checks event.req.context?.clientAddress and event.req.ip — both undefined on the converted request

Fix

Replace the fromWebHandler shorthand with an explicit eventHandler that extracts the IP from the outer Nitro h3 v1 event and attaches it to request.context before calling handler.fetch:

import { eventHandler, getRequestIP, toWebRequest } from 'h3'
import handler from '${ssrEntryFile}'
export default eventHandler((h3Event) => {
  const ip = getRequestIP(h3Event) ?? getRequestIP(h3Event, { xForwardedFor: true })
  const request = toWebRequest(h3Event)
  if (ip) {
    request.context = Object.assign(request.context || {}, { clientAddress: ip })
  }
  return handler.fetch(request)
})

h3 v2's H3Event constructor reads req.context as the event context, so getRequestIP subsequently finds event.req.context.clientAddress. The socket-based IP is tried first; xForwardedFor is used as fallback for reverse-proxy deployments.

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.