Yes I know I am posting about a browser error, but I keep having this error across multiple browsers. So firstly, my nextjs app in development mode is running on http://localhost:3000/ but since a few weeks it keeps getting this weird error: "ERR_TOO_MANY_REDIRECTS". This is just a chrome specific browser, but if try the Zen Browser which is based on Firefox not on Chrome I am getting a different error which says the page is not working properly. I tried fixing the error as the Google Chrome docs suggested but it did not fix it. For those who do not know it has something too do with website data and the docs tell you to remove all of which from Chrome, this is not helping. Does anyone know how to fix it or what the problem might or where I can get help for it, because due to this annoying error message I can check the front page of my app. Thanks
#ERR_TOO_MANY_REDIRECTS
1 messages · Page 1 of 1 (latest)
🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord
🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize
✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)
Are you using cloudflare?
For what?
for example for ddos protection. Are you using cloudflare?
No I am not using cloudflare in any kind of way
But what could be the cause of the problem then?
it may have to do with your middleware, translations, hostings, ... there can be many places where the issue comes from. Finding the cause of the issue is too much effort for me, sorry
You are getting the same error, it's just that browsers report it differently.
Look for bugs in your middleware as it is the most common cause or some other redirect loop.
Show your package.json, and also if you have a middleware.ts, what does it look like.
It was my middleware, not it is working again. It had an old feature still being used. Thanks for you help