Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
404 (Not Found) index page when building multi-tenant app
See original GitHub issue🐛 Bug Report
I’m building a multi-tenant Next.js app. After adding next-i18next into the mix, the homepage (index page) started ending on 404 Not Found. All other pages work just fine, only index page gets 404. When I comment out next-i18n (the config in next.config.js in particular) everything starts just working again. See the prepared bug reproduction below
To Reproduce
Here I’ve prepared a minimal reproducible example of this problem.
Expected behavior
The index (home) page should load ok even with next-i18next.
Your Environment
- runtime version: node v14.18.3
- next-i18next version: 12.1.0
- next.js version: 13.0.3
- os: MacOS
Issue Analytics
- State:
- Created 10 months ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m not saying you have to remove the config, I’m only saying, this issue is most probably not caused by next-i18next but by the Next.js i18n routing feature => https://nextjs.org/docs/advanced-features/i18n-routing
😅 ohhh… I see, now I get it. Well, thanks again 😃