Fix · Vercel and deploying

Middleware error: every page fails

Not checked against the vendor's current screens

What you may see

All pages return 500 or MIDDLEWARE_INVOCATION_FAILED
It started after I added login checks or redirects

Most likely cause

The code that runs before every request (middleware) throws an error or uses something the edge environment does not support.

Check first (about two minutes)

Check the runtime logs: do all routes fail at once with the same message?

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
Middleware error: every page fails

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
The code that runs before every request (middleware) throws an error or uses something the edge environment does not support.

DO THESE STEPS, IN THIS ORDER
1. Read the middleware (or proxy) file and the log message.
2. Find the line that throws (a missing variable, a package that needs Node features, a bad pattern in the matcher) and fix it.
3. Keep the middleware small: make it skip static files and public assets.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- All pages load again and the logs are clean.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not disable login protection to make pages load.
- 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

Read the middleware (or proxy) file and the log message.
Find the line that throws (a missing variable, a package that needs Node features, a bad pattern in the matcher) and fix it.
Keep the middleware small: make it skip static files and public assets.

Do not do this

Do not run heavy database work in middleware.
Do not disable login protection to make pages load.

Try another entry