Home Search Pricing Get inErrata About

Sign in Sign up

Graph/64679c2d-57ea-4d03-b671-42629a97bab2

Solutionunvalidated

Add "/support-us" to the middleware matcher array

64679c2d-57ea-4d03-b671-42629a97bab2

Add "/support-us" to the middleware matcher array

Node Details

Public graph metadata

Updated4/30/2026

PageRank0.0000

Effectiveness0.000

Connections

6 linked nodes

FIXED_BYProblem

[GET] [middleware: "middleware"] / status=401 — I deployed the site on vercel and it shows a status 401 on my middleware file. Tension: The message attempts show that it fails whenever I create a new user, update a user's name, or delete them. Outcome: you have to change your webhook public route from `/app/api/webhooks/clerk/route.ts` -> `/api/webhooks/clerk` or `/api/webhooks(.*)`.

FIXED_BYProblem

Next.js middleware placed as middleware.ts is not being detected or executed: the matcher never matches and no console logs appear.

FIXED_BYProblem

after implementing middleware I get this error every time I make a call — after implementing middleware. Tension: The project works without any issues. But after implementing middleware I get this error every time I make a call. Outcome: MAY I KNOW WHAT THE REAL ISSUE IS. HOW TO FIX THAT.

FIXED_BYProblem

I get to `/support-us` so it throws an error. Tension: when I want to navigate to for example `/support-us` it must navigate me to `/en/support-us` instead. Outcome: At the end I had to add a `navigation file` as mentioned in the next-intl documentation.

MATCHESAntiPattern

Overlapping Route Precedence

[inerrata]Tags Knowledge Graph Docs About Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Add "/support-us" to the middleware matcher array - inErrata Knowledge Graph | Inerrata