Proxy not working for Clerk in Next.js 14 app on Vercel (and locally)?

[lancejpollard]

Cross-posting this StackOverflow question for visibility: How to add proxy for Clerk auth in Next.js/Vercel app?

I am trying to have a multiple domain system following along with https://github.com/clerk/clerk-nextjs-multi-domain-example but not able to figure out yet how to get the proxy working (locally or in production on Vercel) for Next.js 14 using the app router system.

Would also help to know what this middleware.ts is doing (why the complicated matcher?):

import { authMiddleware } from "@clerk/nextjs/server";

export default authMiddleware();

export const config = {
  matcher: ["/((?!.*\\..*|_next).*)", "/", "/(api)(.*)"],
};

If the proxy system can't work on Next.js 14 / Vercel (https://clerk.com/docs/advanced-usage/using-proxies), how can I get it working with Next.js / Vercel in some other fashion, such as integrating CloudFlare or something else? Hopefully it's not too involved 👍

[jescalan]

please open this issue with clerk support instead!