You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everyone!
After implementing next-intl into my next.js application in production, I get a 1000 DNS points to forbidden IPerror when trying to log in to the site. As I understand it, the problem lies in the Middleware that next-intl provides. I tried disabling intlMiddleware and the site worked completely. I turned on intlMiddleware back, I'm facing this problem. I tried removing x-frowarded-for and cf-connecting-ip from headers as described in the Clodflare documentation, but nothing helped. I also noticed that the redirect works out and I already get the error itself, being in some locale. The application is deployed in the Coolify environment version 3.12.36. How can I fix this problem?
Verifications
I've verified that the problem I'm experiencing isn't covered in the docs.
I've searched for similar, existing issues on GitHub and Stack Overflow.
I fixed it! The problem was the incorrect use of two middleware (auth.js and next-intl) together. The branch helped in the solution #596 . Thank you all!
Hello, I have the same error with the same setup (coolify + cloudflare). I tried the solution in #596 but still have the error :( (when returning the next-intl middleware in the next auth Middleware).
@ClooudNine Can I know how did you make it ? Thanks a lot.
Description
Hello everyone!
After implementing next-intl into my next.js application in production, I get a 1000 DNS points to forbidden IP error when trying to log in to the site. As I understand it, the problem lies in the Middleware that next-intl provides. I tried disabling intlMiddleware and the site worked completely. I turned on intlMiddleware back, I'm facing this problem. I tried removing x-frowarded-for and cf-connecting-ip from headers as described in the Clodflare documentation, but nothing helped. I also noticed that the redirect works out and I already get the error itself, being in some locale. The application is deployed in the Coolify environment version 3.12.36. How can I fix this problem?
Verifications
Mandatory reproduction URL
https://github.com/ClooudNine/cloud-retainer
Reproduction description
Steps to reproduce:
Expected behaviour
I expect next-intl middleware not to cause 1000 DNS points to prohibited IP errors
The text was updated successfully, but these errors were encountered: