"Too many redirects" error on Next.js Zone (v15.5.25) after upgrading Root Zone to v16.3.4
Unanswered
Mini Satin posted this in #help-forum
Mini SatinOP
We run a multi-zone Next.js application. Previously, our setup worked perfectly with the following versions:
Root and primary zones: Next.js v16.2.9
Legacy zone: Next.js v15.5.9
The Problem
We recently upgraded our root and primary zones to v16.3.4, and updated the legacy zone to v15.5.25.
Local Environment (npm run dev): Everything functions exactly as expected across all zones.
Production Environment (AWS Amplify): The v16.3.4 zones work perfectly, but navigating to the v15.5.25 zone throws a "redirected you too many times" (ERR_TOO_MANY_REDIRECTS) error.
Our Constraints
We plan to upgrade the legacy zone to v16 in 2 to 3 months. Until then, we must keep this zone on v15 while keeping the root and other zones on the latest version.
How can we resolve this routing conflict occurring specifically within the AWS Amplify hosting environment?
Root and primary zones: Next.js v16.2.9
Legacy zone: Next.js v15.5.9
The Problem
We recently upgraded our root and primary zones to v16.3.4, and updated the legacy zone to v15.5.25.
Local Environment (npm run dev): Everything functions exactly as expected across all zones.
Production Environment (AWS Amplify): The v16.3.4 zones work perfectly, but navigating to the v15.5.25 zone throws a "redirected you too many times" (ERR_TOO_MANY_REDIRECTS) error.
Our Constraints
We plan to upgrade the legacy zone to v16 in 2 to 3 months. Until then, we must keep this zone on v15 while keeping the root and other zones on the latest version.
How can we resolve this routing conflict occurring specifically within the AWS Amplify hosting environment?
8 Replies
Mini SatinOP
Route53
@Mini Satin Route53
no proxy? CDN or similar?
@Mini Satin?
Mini SatinOP
@B33fb0n3 We are hosting the frontend on AWS Amplify Hosting (which manages CloudFront under the hood), with Route 53 pointing to Amplify.
Mini SatinOP
@B33fb0n3 ?
Mini SatinOP
@B33fb0n3 Any update?
@Mini Satin up to now I don’t have enough information to solve this issue, sorry.