Self-signed Certificate error on Dedicated Server when using handleI18nRouting middleware #2019
Unanswered
AndreyPerunov
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello community,
I am getting an
Internal Server Errorwhen I navigate to/or/ento the dev version of application.Error log:
Environment:
next.js v15.2.4nginxas reverse proxyDockernext-auth v5.0.0-beta.29for authenticationnext-intl v3.26.4for internationalizationProblem isolation:
The app works fine until I add
handleI18nRoutingfrom next-intl middleware.handleI18nRouting(req)to the top of the middleware chain, I immediately get the error.My middleware.ts:
Assumptions
First, I thought that the problem is with redirect, so I do this:
Result: I didn't get an error.
Question:
What could be causing this issue? Is there a known problem with combining
next-intlmiddleware andauth.jswhen using a self-signed certificate in development?Any guidance would be appreciated!
Beta Was this translation helpful? Give feedback.
All reactions