Fix · Vercel and deploying

Too many redirects (redirect loop)

Blocks your workNot checked against the vendor's current screens

What you may see

The browser says this page isn't working: redirected you too many times
The page keeps loading and then fails

Most likely cause

Two rules send the visitor back and forth, for example www to non-www and back, http to https and back, or a login redirect that never ends.

Check first (about two minutes)

Try the address in a private window with cookies cleared: does it still loop?
List every place redirects can be set: the host, the domain company, the framework config, middleware, and the code.

The fix prompt

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

The exact error or what you see

What you did before it happened

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a patient senior engineer who deploys websites on Vercel every day and explains it to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

Menu and button names change over time. If you cannot find a button or page I mention, say so and tell me what to look for instead of guessing.

THE PROBLEM
Too many redirects (redirect loop)

THE EXACT ERROR OR WHAT I SEE
[paste the exact error here]

WHAT I DID BEFORE IT HAPPENED
[write in a few words what you did before it happened]

MOST LIKELY CAUSE
Two rules send the visitor back and forth, for example www to non-www and back, http to https and back, or a login redirect that never ends.

DO THESE STEPS, IN THIS ORDER
1. Run curl -I -L --max-redirs 10 <address> and show me the chain of addresses and status codes.
2. Find which two rules fight (host settings, domain company forwarding, a proxy service, framework redirects, middleware, login checks).
3. Remove or change ONE rule so there is a single clear path (for example one canonical address, one https rule).
4. Retest with curl and in a private window.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- curl shows at most one redirect, then a 200 answer.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not remove the https redirect altogether.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Run curl -I -L --max-redirs 10 <address> and show me the chain of addresses and status codes.
Find which two rules fight (host settings, domain company forwarding, a proxy service, framework redirects, middleware, login checks).
Remove or change ONE rule so there is a single clear path (for example one canonical address, one https rule).
Retest with curl and in a private window.

Do not do this

Do not turn on a second redirect somewhere else while testing.
Do not remove the https redirect altogether.

Try another entry