I just checked and it doesn’t look like it’s 404ing everything. There’s no index.html in your deploy. You’re probably rendering it on server side by using Netlify Functions. However, if you try Quartexx Management, it loads the page correctly.
So the rule works correctly, but it won’t be able to distinguish between pages that don’t exist and pages that are rendered on the fly.
Unfortunately, there’s no way for files rendered server-side. For the redirect rule to work, you’d have to make sure the static version of the files exist.
But I believe, there’s another way from within Next.js to set a custom 404 page - I’m not sure, but I think I’ve seen such a setup somewhere. I am not a Next.js user myself, so can’t confirm, but I’ll roll this to the team to see if they have any other suggestions.
It has to be one of those - can’t be both. From what I checked, your last deploy was on October 4, so it’s still the same as the one I talked about last time and it’s rendering server-side - not static.
With your current setup, there’s a workaround for you though - however it might not be very acceptable. But here you go. You could create a static 404.html in your publish directory and Netlify will automatically show that page for all 404 assets without any redirect needed. The problem with that is, you won’t get language specific 404 pages - it would be same page for the entire website. But there’s a workaround for that:
You could setup language or country based redirects on that 404.html page so you could try and get the behaviour you need. But the problem with that is, 404 assets would return a status code of 301/302 to browsers/search-engines, etc. The end user might not notice it as they’ll see the 404 page, but the tools might be confused.