Cloud Run and Resources not loading via the LoadBalancer routing

[TalalBhatti]

Summary

Everything works on Cloud Run, but behind the load balancer the app fails with partial asset loading. Network traces show static resources being fetched from the load balancer domain instead of the Cloud Run service URL.

Additional information

No response

Example

No response

[hyattc1]

The problem usually comes up because Next.js tries to serve static files relative to the domain it’s running on. When you put it behind a load balancer, those requests can get pointed at the LB domain instead of the Cloud Run service.

A couple things you can try:

• In next.config.js, set an assetPrefix that matches your Cloud Run service URL
• Double-check that the load balancer is rewriting paths the way you expect
• If you’re using a custom basePath, make sure that lines up too.

Easiest way to confirm is open the Network tab and see which files are 404’ing. That will usually show you if it’s just a prefix mismatch.