You would have to share your middlewarenwith us

Middleware*

This feels like a problem in the reverse proxy, next js https is experimental so i would have to see your architecture and middleware to conclude @Sloth bear

@Pygmy Nuthatch @American Chinchilla

I have this problem even if i have a simple middleware like :

export function middleware(request: NextRequest) {
   return NextResponse.next()
}

My structure is :

src
   app
   components
   middleware.ts

Ok but how is the traffic routed to the server

I did not understand

Is the next instance in https mode

Im isking if the traffic is decrypted before it hits the server

I did not touch my next config for https.
I was always worked with http.
The funny thing is when i remove my middleware, problem is gone and routes are ahown.
But when i put middleware my route and chunks are not load.
I have no idea what to do ;((

Huh well that is essential info

What info yoh need? Tell me to give it to you

Wait

Do you have a matcher

Nope.
I was added matcher too. no effect

What

This may be a bug

Yeah bro sorry this is the end of my knowledge

Bug of what? Next?

Thanks bro 🙂

I would think

export const config = {
matcher: [
/*
* Match all request paths except for the ones starting with:
* - api (API routes)
* - _next/static (static files)
* - _next/image (image optimization files)
* - favicon.ico, sitemap.xml, robots.txt (metadata files)
/
'/((?!api|_next/static|_next/image|favicon.ico|sitemap.xml|robots.txt).)',
],
}

If this doesn’t work

Then yeah not sure

In middleware add that*^

At bottom

Still have the problem :((

Could it be the cloudflare issue??

Its possible but if it works without middleware i doubt it

Problem solved!
It was from webserver and haproxy(DevOps issues)

Thank you guys

Damn
It was Nextjs bug😧

Look at here :
https://github.com/vercel/next.js/issues/58764

@Pygmy Nuthatch you were right... It's Nextjs bug