I've tried everything I can think of, any idea on how to debug this?

I’m pretty sure this is a known issue. https://github.com/vercel/next.js/issues/58400

In my case it shows the browser not-found page

Not the Next.js one

Looks like a PPR issue

one of thousand, PPR breaks a lot of stuff, including parallel and intercepting routes

It works without PPR, but Links behave weirdly

The url is changed but no rerender :/

yeah that's a known issue

with Links not working out of error pages

Alright, I'll just router push

Thanks a lot for the insight! Hope PPR gets better

hope it gets usable lol

Almost as hyped as View Transitions API

I'm still unable to deploy my app to Vercel with PPR on

don't get me wrong, PPR is amazing - will be, when it actually works

until then you can looks at the output locally, get hyped, then turn it off because it breaks so many things

oh nice, updated to 14.0.3-canary.6 and now intercepting routes stopped working on Vercel, but they work locally

Yeah agreed

Was .6 pushed just now?

20 minutes ago

Cool

I'm hyped with the new features as of late

error pages throwing 500 in Vercel

also a new feature of 14.0.3-canary.6

Yeah canary is canary lately

I have this same bug! And I can't fix it. I don't have Partial Prerendering and I'm running on 14.0.1. This is my project structure. Any clues on how to fix it? Locally I see my 404 page but on Vercel it renders the default 404 page.