Context

Frontend: Nuxt 3 with ssr: true (Nitro, server-rendered initial load).
Backend: Laravel API with rare IP-based rate limiting.
Topology (initial render): Browser → Nuxt SSR → Laravel API.

Problem

On the initial SSR render, requests to Laravel come from the Nuxt server’s egress IP, not the end-user’s IP. That means from Laravel’s perspective, many users “collapse” into one (or a few) IPs. Laravel’s IP limiter can then throttle or block the SSR server, breaking the initial page render for everyone behind it.

After hydration, if the browser fetches the API directly, Laravel sees the client IP. But if we use a BFF/proxy pattern (Nuxt server routes proxying to Laravel), Laravel still sees the Nuxt server IP unless we forward the client IP and trust it correctly.

What’s the recommended pattern for Nuxt 3 SSR + Laravel to avoid collapsing many users into the SSR IP for rate limiting?

How to handle the fact that the backend blocks the frontend server in general? Am I missing something here?